Skip to main content
Glama
monzo-mcp

monzo-mcp

monzo_sync

Sync Monzo transactions, balances, and pots into a local cache for spending analysis and transaction search across historical data beyond the 90-day API window.

Instructions

Sync transactions, balances, and pots from the Monzo API into the local cache.

Fetches up to 11 months of history (within SCA window) or falls back to the last-synced timestamp / 90 days. Handles pagination and auth-hold deduplication automatically. Declined card attempts are not stored. Only current and joint accounts are synced; any other is listed as skipped.

Args: account_type: "personal", "joint", or None to sync both since: Optional ISO date ("2026-01-01") or datetime ("2026-01-01T14:30:00Z") to start the backfill from, overriding last-sync resumption. Reaching beyond ~90 days only works inside the post-auth SCA window.

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

Input Schema

NameRequiredDescriptionDefault
sinceNo
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_syncOutput",
      -  "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. Changed1 schema field changedv0.2.1
    • addedInput schema / properties / since
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Since"
      +}
  4. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the 11-month SCA-bounded window, the fallback to last-synced/90 days, automatic pagination and auth-hold deduplication, that declined card attempts are not stored, and that non-current/joint accounts are skipped rather than failing. These are exactly the side-effect and scope traits an agent needs before invoking a mutating sync.

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 purpose is front-loaded in one sentence, followed by scoped behavioral notes and a clean Args block. There is minor duplication, since the SCA window constraint appears both in the body and again in the 'since' entry, but the structure is easy to scan and nothing is padded.

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 two-parameter tool with no annotations and no output schema, the description covers scope, fallbacks, deduplication, and exclusion rules thoroughly. It stops short of describing what the call returns (counts, per-account skipped results) or whether it is idempotent/long-running, which would matter for an agent sequencing follow-up calls.

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%, but the description fully compensates: it enumerates the account_type values including the None-means-both default, and specifies the accepted 'since' formats (ISO date and full datetime with example) plus its override semantics against last-sync resumption. Nothing about either parameter is left ambiguous.

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

Purpose5/5

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

The opening sentence gives a specific verb and resource set ('Sync transactions, balances, and pots from the Monzo API into the local cache'), which is immediately distinguishable from the read-only siblings (monzo_list_transactions, monzo_get_balance, monzo_list_pots). An agent can tell this is the cache-populating operation without opening the schema.

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 description explains resumption behavior and the SCA window limit, which tells an agent when a backfill will succeed, but it never explicitly says 'call this before the list/search tools to refresh the cache' or names a condition that selects it over a sibling. No exclusions relative to alternatives are given.

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