Lunch Flow MCP provides three read-only financial tools with clear naming, explicit Zod schemas, and toolAnnotations (readOnlyHint). However, output schemas are entirely undocumented, the actual data structures returned by the API are never formally specified in the server code, forcing LLMs to infer from JSON string responses. Parameter descriptions are present but minimal (10-15 chars typical). No pagination parameters despite tools that likely return lists. Error handling is basic: generic catch blocks and HTTP status checking without actionable recovery guidance. The server is STDIO-only, which is a hard cap at 50 for protocol readiness, but definition quality stands independently at 62 due to present naming, schema inputs, and annotations.
Get the current balance for a specific bank account. Returns available and current balance information.
Get transactions for a specific bank account. Returns transaction history including date, amount, description, merchant, and category information.
Get a list of all connected accounts for the authenticated user. Returns account details including name, institution, provider, currency, and status.
Output schemas completely undocumented. Tools return raw JSON.stringify() responses with no schema definition, making it impossible for LLMs to predict return structure and plan downstream calls.
Error handling provides no recovery guidance. Catch blocks and HTTP errors are logged as plain text (e.g. 'Error executing tool: [message]'). No indication of whether errors are retryable, what the LLM should do next, or how to self-correct.
No pagination parameters on list_accounts or get_account_transactions. If accounts or transaction lists are large, responses will bloat the context window. No limit, offset, page_size, or cursor parameters to constrain results.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 57 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 44 | - | v1 |
Parameter descriptions are minimal (10-15 chars). 'The numeric ID of the bank account to get transactions for' is present but brief; no guidance on expected range, format validation, or what happens if the ID does not exist (beyond a generic 404).
Generic error messages do not include the invalid value or constraint violated. Example: 'Account with ID 123 not found' is present for 404s, but non-404 errors only report 'Error: [status] - [body]', offering no LLM-actionable detail.