Skip to main content
Glama
monzo-mcp

monzo-mcp

monzo_list_pots

List all savings pots and balances for a Monzo personal or joint account. Returns pot names, current balances, and records balance snapshots for tracking.

Instructions

List all pots (savings buckets) for a Monzo account.

Args: account_type: "personal" or "joint" (default: "personal")

Returns the account the pots belong to, plus pot names and balances. Also records balance snapshots.

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

Input Schema

NameRequiredDescriptionDefault
account_typeNopersonal

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_potsOutput",
      -  "type": "object"
      -}New value: +null
  2. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / account_type / enum
      Added value: +[
      +  "personal",
      +  "joint"
      +]
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a non-obvious side effect ('Also records balance snapshots') and the return shape (account, pot names, balances), which is real value. It says nothing about auth requirements, whether the snapshot write is consequential, or rate limits.

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 a short Args block and a Returns block. The docstring scaffolding ('Args:', 'Returns the account...') is slightly formulaic but each line carries information 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 one-parameter read tool with no output schema, the definition covers purpose, the sole argument, the return contents, and a side effect. Only the safety/authorization profile is absent, which is a modest gap for a low-complexity tool.

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 coverage is 0%, so the description must carry the parameter meaning, and it does: account_type is explained as 'personal' or 'joint' with a stated default. That mostly restates the enum and default already present in the schema, but for a single-parameter tool it leaves no ambiguity about what the argument selects.

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 description names a specific verb and resource ('List all pots (savings buckets)') and clarifies what a pot is, which separates it from monzo_list_accounts and monzo_get_balance by resource type. It never explicitly states the difference from those siblings, so it falls short of a 5.

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 only implied: the reader can infer this is the tool for enumerating pots, and the default account_type is given. There is no statement of when to prefer it over monzo_list_accounts or monzo_get_balance, and no prerequisites or exclusions.

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