Repository navigation
Speed up MCP expense entry and parallelize database reads - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Routine expense entry now has an explicit one-tool-call path when the conversation already contains verified member IDs and established date/currency defaults. MCP instructions and tool descriptions tell clients to reuse that context, avoid history scans and redundant verification, and confirm a successful write briefly. Unresolved identities and shared participants still require clarification.
The service loads current trip/members and checks requestId concurrently, removing one sequential database wait while keeping membership validation and duplicate protection. Wallet membership is not cached.
Validation: all 156 tests, including a regression that holds membership loading open and verifies the duplicate lookup starts before it completes, plus the production build and diff checks. The uploaded tree matches the tested local tree. No real expenses were added during this change.
Deploy the updated standalone MCP server and refresh tool descriptions/initialization instructions in clients or static gateways. GitHub Pages deployment does not update MCP.