Skip to main content
Glama

Update bank account

crunch_update_bank_account
Idempotent

Update a bank account's details while preserving unchanged fields. Sort code and account number stay locked once the account has a bank feed or reconciled entries.

Instructions

Change a bank account's details. Only the fields you pass change; the rest are kept. Sort code and account number can't be changed once the account has a bank feed or reconciled entries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bank_account_id": "<bank_account_id>"
    },
    "name": "crunch_update_bank_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoBIC
ibanNoIBAN
extraNoAdditional raw fields for the request body, using Crunch's own field names (advanced). Merged last.
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
personalNoA personal (not business) account used for business payments
bank_nameNoBank, for example Starling
sort_codeNoSort code, for example 12-34-56
account_nameNoName on the account
display_nameNoName shown in Crunch, for example Business Current Account
account_numberNoAccount number
bank_account_idYesBank account ID (see crunch_list_bank_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: PATCH-style semantics (only passed fields change, others preserved) and a hard constraint that sort code and account number are locked once a bank feed or reconciled entries exist — a failure mode an agent would otherwise hit blindly.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and immediately followed by the two operational rules that matter most. No filler, no restatement of the title or annotations.

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?

With 11 parameters, full schema coverage, annotations and no output schema, the description supplies the two things structured data can't: mutation semantics and the immutability precondition. It stops short of covering permission requirements or how dry_run output should be interpreted, which would complete the picture for a write 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 description coverage is 100%, so the baseline is 3, and the description earns an extra point by attaching a meaningful precondition to sort_code and account_number that the schema does not state. It says nothing extra about dry_run, extra, bic/iban, or personal, so it is not exhaustive.

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?

"Change a bank account's details" names a specific verb and resource, and the partial-update sentence clarifies the mutation model. It doesn't explicitly contrast with siblings like crunch_create_bank_account or crunch_set_default_bank_account, but the intent is unmistakable.

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?

The description establishes when this tool applies (modifying an existing account) and implicitly rules out creation, but it gives no explicit routing to alternatives such as set_default or archive, nor any mention of how dry_run should be used to preview changes.

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

Deploy Server

Other Tools