Skip to main content
Glama
monzo-mcp

monzo-mcp

monzo_spending

Analyse spending from cached Monzo transactions by month, category or account type. Returns category summaries or individual transactions, auto-syncing the cache when stale.

Instructions

Analyse spending from cached Monzo transactions.

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

Every result carries account_type, echoing the filter applied and null when unfiltered, so a zero total says which account it measured.

Args: month: Month in YYYY-MM format (default: current month) category: Filter by category, e.g. "groceries", "eating_out", "transport" account_type: "personal" or "joint" (default: all) detail: If true, return individual transactions instead of category summary

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_spending"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNo
detailNo
categoryNo
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_spendingOutput",
      -  "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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the implicit cache sync triggered on stale data, the default month/account scope, and the `detail` output-shape switch. It omits the cost/latency of the auto-sync, whether it can fail on auth, and pagination or size limits for detail mode.

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 claims are front-loaded in the first two sentences and the result-shape note follows, with parameters listed compactly. The Args docstring style is slightly developer-facing but contains no filler sentences.

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 4-parameter analysis tool with no annotations and no output schema, the description covers purpose, side effects, defaults, and parameter formats. The remaining gap is the shape/contents of the returned summary, which the agent has no other structured source for.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it mostly does: it gives the `month` format (YYYY-MM) and its effective default of the current month, sample `category` values, the `account_type` options and default of all, and the meaning of `detail`. The only gap is what fields the category-summary or per-transaction payloads actually contain.

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?

States a specific verb+resource ("Analyse spending from cached Monzo transactions") and clarifies that the output is either a category summary or individual transactions via `detail`. It is distinguishable from `monzo_list_transactions`/`monzo_search_transactions` by being an aggregation tool, but it never explicitly names those siblings to sharpen the distinction.

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 rather than stated: the auto-sync sentence tells the agent it need not call `monzo_sync` first, and the default month/category/account behavior hints at the unfiltered case. However, there is no explicit "use this when..." or "use X instead for..." guidance against the six sibling tools, leaving the choice to inference.

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