Skip to main content
Glama

Create bank account

crunch_create_bank_account

Add a bank account to Crunch so payments can be recorded against it.

Instructions

Add a bank account to Crunch so payments can be recorded against it.

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": {
      "display_name": "<display_name>",
      "bank_name": "<bank_name>"
    },
    "name": "crunch_create_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_nameYesBank, for example Starling
sort_codeNoSort code, for example 12-34-56
account_nameNoName on the account
display_nameYesName shown in Crunch, for example Business Current Account
account_numberNoAccount number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the write profile is covered structurally. The description adds only the downstream purpose of the record; it says nothing about duplicate-account handling (relevant given non-idempotency), permission requirements, or what a successful create returns.

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?

A single efficient sentence with no filler, and the purpose is front-loaded. It is arguably too terse for a 10-parameter mutation tool, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter create with a nested free-form 'extra' object and no output schema, the definition covers only the bare purpose. The schema documents fields well, but the description gives no help on which fields actually enable payment recording or how to avoid duplicate accounts.

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 100% across all 10 parameters, including the nested 'extra' object and the dry_run preview flag, so the schema does the heavy lifting. The description adds no meaning beyond it, which is the expected baseline when coverage is complete.

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 uses a specific verb+resource ('Add a bank account to Crunch') and adds the business reason ('so payments can be recorded against it'). It does not explicitly differentiate from siblings like crunch_update_bank_account or crunch_set_default_bank_account, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as updating an existing account instead of creating a new one. The implied usage is 'when you need a new bank account', which the agent must infer.

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