Skip to main content
Glama

List bank accounts

crunch_list_bank_accounts
Read-only

List business bank accounts with balances, sort codes, account numbers, default flags, bank feed status, and unmatched statement counts. Use returned IDs when recording payments.

Instructions

List the business's bank accounts with their current balance, sort code and account number, default flag, bank feed state and how many statement entries still need matching. Use the IDs when recording payments.

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": "crunch_list_bank_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full objects from the API instead of compact summaries (larger)
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value
statusNoWhich to list: active (default), archived or all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine return-content context (default flag, bank feed state, count of unmatched statement entries) that the annotations do not, but says nothing about pagination, ordering, or the effect of the status/search filters.

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?

Two tight sentences with the resource and its returned fields front-loaded and no filler. The trailing payments hint earns its place, though the sentence is long and slightly list-heavy.

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?

No output schema exists, so the description must convey what comes back, and it does so by enumerating the salient fields including the matching backlog. Missing is any note on result volume or how the optional filters interact, which is a small gap for a five-parameter list tool.

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%, with all five parameters documented including the status enum, so the schema carries the burden and the baseline is 3. The description adds no meaning beyond it — it never mentions raw, limit, fields, search, or status filtering.

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 ('List') and resource ('bank accounts') and enumerates the fields surfaced (balance, sort code/account number, default flag, feed state, unmatched statement count), which is well beyond a tautology. It does not explicitly distinguish itself from the sibling crunch_get_bank_account, so an agent must infer that this one returns the collection while that one returns a single record.

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?

'Use the IDs when recording payments' hints at downstream usage but is not a when-to-use-vs-alternatives rule. There is no statement about when to prefer crunch_get_bank_account or crunch_list_bank_account_payments, and no preconditions or exclusions are given, leaving usage implied by the tool name.

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