Skip to main content
Glama

Binyan.im · בניינים

Matched bank transactions

list_matched_bank_transactions
Read-only

List bank transactions already matched in a building, optionally between from and to (YYYY-MM-DD), with what each one is matched to: the payment, expense, refund or cash transfer it covered, including every part of a split match. 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>"
    },
    "name": "list_matched_bank_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoInclusive end day, YYYY-MM-DD. Defaults to no upper bound.
fromNoInclusive start day, YYYY-MM-DD. Defaults to no lower bound.
limitNoMaximum matched transactions to return. Defaults to 200.
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 context beyond that: the result includes each matched counterparty and every part of a split match, plus the bank-sync prerequisite. It omits anything about the default/maximum result size or ordering, which the schema only partially covers.

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?

One dense sentence covering scope, optional range, return content and prerequisite, with the core scope front-loaded. It is long but every clause carries information; a small cost is that the prerequisite trails at the end rather than being surfaced early.

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 a four-parameter read-only list tool with no output schema, the description adequately explains what comes back (matched entity per transaction, split parts) and the environment prerequisite. Remaining gaps — pagination behavior and result ordering — are minor.

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?

At 75% schema coverage the schema already documents from/to as inclusive YYYY-MM-DD bounds and limit as 1-500 defaulting to 200. The description only restates the optional date range and adds nothing about limit semantics or buildingId, so baseline 3 applies.

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 and resource ('List bank transactions already matched in a building') and adds the returned payload semantics (the payment, expense, refund or cash transfer it covered, including split parts). The word 'matched' implicitly contrasts with the sibling list_unmatched_transactions, though that sibling is not named explicitly.

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?

A useful prerequisite is given: bank tools only work when a building has bank sync configured. However, there is no explicit when-to-use vs. when-not guidance and no named alternative (e.g. list_unmatched_transactions or reconcile_transaction), so an agent must infer the choice from sibling names.

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