Monzo-MCP has well-structured tool definitions with explicit schemas (Zod) and clear naming conventions (verb_noun pattern). However, parameter descriptions are systematically missing or null across all 14 tools, which is a critical gap. Tool descriptions are present and reasonably detailed (avg ~120 chars), but lack guidance on when to use each tool vs. alternatives. No output schemas are documented. Error handling exists but lacks recovery guidance. The server correctly gates write tools behind MONZO_MODE=write, showing security awareness.
Add or update metadata key/value pairs on a transaction. Pass an empty string as the value to remove a key.
Register an uploaded attachment against a transaction. Call attachment_upload first to get the file_url.
Request a temporary upload URL for a file. Returns file_url and upload_url. PUT the file bytes to upload_url separately, then call attachment_register.
Create a basic feed item in the user's account feed.
Read the balance for an account. If account_id is omitted, defaults to the user's single open uk_retail account.
Retrieve a receipt by its external_id.
All parameter descriptions are null or missing. The schema shows `"description":null` for nearly every parameter (account_type, account_id, since, before, limit, expand_merchant, etc.). LLMs cannot infer parameter meaning from names alone, a 'limit' param needs context (items? bytes? seconds?). This violates pattern:tool-description and forces LLMs to guess.
No output schemas documented. Tool descriptions do not specify what fields are returned or their types. For example, list_accounts returns account objects but the structure is not documented. Agents cannot plan downstream calls or extract the right data without knowing the response shape.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2025-06-18+ | v2 |
Retrieve a single transaction by id.
List the authenticated user's accounts. Optionally filter by account_type (e.g. 'uk_retail', 'uk_retail_joint').
List pots for a current account. If current_account_id is omitted, defaults to the user's single open uk_retail account.
List transactions for an account. Supports pagination (since/before/limit) and expanding the merchant. If account_id is omitted, defaults to the user's single open uk_retail account.
List webhooks registered for an account. If account_id is omitted, defaults to the user's single open uk_retail account.
Deposit funds from a source account into a pot. Amount is in minor units (pennies for GBP). dedupe_id must be unique per logical transfer.
Withdraw funds from a pot to a destination account. Amount in minor units. Blocked if the pot has 'added security' enabled.
Verify the current access token and return information about the authenticated user (GET /ping/whoami).
Error handling lacks recovery guidance. The code throws generic errors like 'No open uk_retail account found' but does not guide the LLM on next steps (e.g., 'Try list_accounts() to see available accounts'). Errors should be actionable per pattern:recovery-guide.
Pagination not fully documented. list_transactions accepts since/before/limit but no documentation of what 'since' accepts (RFC3339 timestamp OR transaction id, this is mentioned in the description but not in the parameter description). No mention of whether results are capped or if there is a next_cursor for continuation.
Destructive operations (pot_withdraw, annotate_transaction) lack confirmation or dry-run support. An agent could accidentally withdraw all funds or delete transaction metadata without a safety gate. Consider adding a 'confirm' parameter or separate confirm_* tools per pattern:confirmation-request.