Skip to main content
Glama
monzo-mcp

monzo-mcp

monzo_get_balance

Retrieve the current balance, today's spending, and currency for a personal or joint Monzo account; also records a balance snapshot for tracking.

Instructions

Get current balance for a Monzo account.

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

Returns balance, spend today, and currency. Also records a balance snapshot.

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

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_get_balanceOutput",
      -  "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.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one genuinely non-obvious behavior — that calling it records a balance snapshot, i.e. a side effect from what looks like a read — which is valuable. It says nothing about auth requirements, failure modes, or whether the snapshot write is consequential.

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?

Front-loaded with the core purpose in one sentence, then return values, then a short args block — compact and easy to scan. Minor redundancy in re-listing the enum and default that the schema already declares.

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 tool with no output schema and no annotations, the description covers the essentials: what is returned and the snapshot side effect. Remaining gaps are peripheral (permissions, rate limits, failure behavior) rather than blockers to correct invocation.

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

Parameters3/5

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

Schema description coverage is 0%, so the description does the work of naming account_type and giving its allowed values and default. However, the enum [personal, joint] and default already exist in the schema, so the description largely restates structured data rather than adding meaning such as what a joint account lookup requires.

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 and resource ("Get current balance") scoped to a Monzo account, and names the return contents, so the agent can tell it apart from list-oriented siblings such as monzo_list_accounts or monzo_list_transactions. It stops short of explicitly contrasting with monzo_spending, which also surfaces today's spend data.

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 "current balance" rather than stated: there is no explicit when-to-use or when-not-to-use guidance, and no mention of why an agent would pick this over monzo_spending for spend figures. The account_type arg hints at personal vs joint selection but doesn't frame a decision.

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