Skip to main content
Glama

List bank account payments

crunch_list_bank_account_payments
Read-only

List payments recorded against a Crunch bank account, filtered by matched or unmatched status. Includes supplier, customer, transfer, salary, dividend and tax payments; paginated newest first.

Instructions

List payments recorded in Crunch against a bank account (supplier payments, customer payments, transfers, salaries, dividends, tax payments...), either reconciled with the bank statement or still unreconciled. Paged; newest first by default.

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>",
      "reconciled": "<reconciled>"
    },
    "name": "crunch_list_bank_account_payments"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoFetch every page (up to max_items) instead of a single page
rawNoReturn the full objects from the API instead of compact summaries (larger)
pageNoPage to fetch, starting at 0 (default 0)
sizeNoResults per page, up to 200 (default 50)
sortNoSort order as field,asc or field,desc, for example postingDate,desc
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value
max_itemsNoWith all=true, stop after this many results (default 1000, at most 10000)
reconciledYestrue for payments matched to bank statement entries, false for those still waiting to be reconciled
bank_account_idYesBank account ID (see crunch_list_bank_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds the useful behavioral facts that results are paged and default to newest-first ordering, which the annotations and sort parameter do not state. It does not mention rate limits or result size, but for a read-only list tool that is a minor omission.

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?

Two sentences, no filler, with the resource scope front-loaded and the pagination/ordering note in a compact trailing clause. Every phrase earns its place.

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 an 11-parameter read-only list tool with full schema coverage and annotations, the description supplies what the schema cannot: the payment categories in scope and the default ordering. It does not explain how all/max_items/limit interact, but the schema covers that, so the remaining gap is small.

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%, so every one of the 11 parameters (including reconciled, all, max_items, fields, search) is already documented in structured data. The description only restates the reconciled distinction that the schema itself explains, so it adds no real meaning beyond it — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (list) and resource (payments recorded in Crunch against a bank account), and enumerates the payment categories covered (supplier, customer, transfers, salaries, dividends, tax). That scope is precise enough to separate it from sibling list tools like crunch_list_expenses or crunch_list_bank_accounts without opening any schema.

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 rather than stated: it is clear the tool is for reading payments tied to one bank account, and the reconciled split hints at the two use cases (matching review vs outstanding reconciliation). However, the description names no alternatives and gives no when-not guidance, so the agent must infer routing on its own.

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