Skip to main content
Glama
monzo-mcp

monzo-mcp

monzo_list_transactions

Query cached Monzo transactions by account type, date range, category, or merchant, with automatic sync when the cache is stale. Use it to search historical spending beyond the 90-day API window.

Instructions

List transactions from the local cache.

Auto-syncs if the cache is stale (last sync before today).

Queries the synced transaction database, not the live API. Bank transfers (faster payments, p2p, bacs) include a counterparty object with the payee name and, where the scheme provides them, sort code and account number.

Returns {"account_type": ..., "transactions": [...]}, where account_type echoes the filter applied and is null when unfiltered.

Args: account_type: "personal" or "joint" (default: all) since: Start date, e.g. "2026-01-01" (inclusive) before: End date, e.g. "2026-02-01" (exclusive) category: Exact category match, e.g. "groceries", "eating_out", "transport" merchant: Merchant name search (case-insensitive, partial match) limit: Max results (default 50)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "monzo_list_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
beforeNo
categoryNo
merchantNo
account_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "monzo_list_transactionsOutput",
      -  "type": "object"
      -}New value: +null
  2. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / account_type / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "personal",
      +      "joint"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does meaningful work: it discloses the implicit write/network side effect of auto-syncing on a stale cache, the staleness caveat of reading cached rather than live data, and the presence of a counterparty object with sort code and account number for bank transfers. It stops short of describing ordering, pagination beyond limit, or what happens when the sync fails.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The behavioral and return-shape information is front-loaded in three tight sentences, and the Args block is justified because the schema has no field descriptions. The block does restate defaults that also appear in the schema, which is minor redundancy rather than bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter read tool with no annotations and no output schema, the description covers the return envelope explicitly, which is exactly what is needed. The remaining gaps are ordering of results, behavior when limit truncates the set, and failure modes of the auto-sync, none of which block a correct first call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description has to document all six parameters itself, and it does: enumerated account_type values, date format with inclusive/exclusive semantics for since/before, exact-match behavior for category with example values, case-insensitive partial matching for merchant, and the default of 50 for limit. This adds genuine meaning the bare schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line states a specific verb and resource ("List transactions") and immediately scopes it to the local cache, with the follow-up clarifying it reads the synced database rather than the live API. It never names the sibling monzo_search_transactions, so the agent must infer the split between listing and searching on its own.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the filter arguments and by the "auto-syncs if the cache is stale" note, which tells the agent it can call this without a prior sync. There is no explicit when-not guidance or pointer to monzo_search_transactions or monzo_sync for the cases where they would be the better choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.