Skip to main content
Glama

Binyan.im · בניינים

Reconcile bank transaction

reconcile_transaction
Destructive

Match, create and match, or ignore a pending bank transaction. Matching to an existing payment marks it paid and replaces its paid date, method, and reference with the bank line. To match one bank transaction to several records, use action match with targets: [{ type, targetId, amount }]. Bank import tools are available only when a building has bank sync configured.

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": {
      "buildingId": "<buildingId>",
      "transactionId": "<transactionId>",
      "action": "<action>"
    },
    "name": "reconcile_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
actionYes
expenseNo
paymentNo
targetsNoSplit match: several payments and expenses for one bank transaction. Each amount is positive; payments count as money in, expenses as money out, and the total must equal the bank amount (e.g. bank -1020 = expense 1500 + payment 480 settled as an offset).
targetIdNo
createFeeNo
buildingIdYes
transactionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "Payment",
      -  "Expense"
      -]New value: +[
      +  "Payment",
      +  "Expense",
      +  "Refund",
      +  "CashBoxMovement"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations flag destructive=true and idempotent=false, and the description adds exactly the context annotations cannot: matching an existing payment overwrites its paid date, method, and reference with the bank line. It also discloses the bank-sync prerequisite. It stops short of explaining what 'create' actually writes (payment vs expense) or how 'ignore' affects the pending transaction afterwards.

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?

Four short sentences, front-loaded with the action enumeration, then the destructive side effect, then the split-match pattern, then the prerequisite. Each sentence carries information, with only mild redundancy against the schema's 'targets' description.

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 9-parameter, nested-object mutation tool with no output schema, the description covers the main decision path and the split-match case but leaves the create branch underspecified — which payload (payment vs expense) is required, what createFee does, and what the caller gets back. Adequate for the match/ignore paths, thin for create.

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

Parameters2/5

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

Schema description coverage is only 11% across 9 parameters, so the description must carry the load, and it does not: the 'payment', 'expense', 'type', 'targetId', and 'createFee' parameters get no explanation at all. Only the 'targets' split-match shape is described, and that text largely duplicates the schema's own description of the same field.

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 names a specific resource (a pending bank transaction) and enumerates the three mutually exclusive operations: match, create-and-match, and ignore. An agent can tell what the tool does immediately, though it does not name any sibling (e.g. list_unmatched_transactions or record_payment) to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It routes between the tool's own actions explicitly — use action 'match' with 'targets' when one bank line covers several records — and states a real precondition: bank import tools only work when a building has bank sync configured. It does not say when to prefer a different tool (e.g. recording a payment directly) or when reconciliation should be skipped.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources