Skip to main content
Glama

Binyan.im · בניינים

Unmatched bank transactions

list_unmatched_transactions
Read-only

List pending bank transactions and their best payment or expense match candidates. 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_unmatched_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 genuinely useful context in the bank-sync prerequisite, which tells the agent about a failure mode. It omits other behavioral details such as result ordering, whether candidates are ranked, and what happens when no candidates exist.

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 short sentences with no filler, and the core purpose is front-loaded ahead of the conditional caveat. It is efficient, though slightly under-specified rather than overly wordy.

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 read-only listing tool with two parameters and no output schema, the definition covers purpose and the bank-sync prerequisite but leaves the return shape of 'match candidates' and the limit parameter unexplained. An agent can call it, but cannot predict the result structure or page size behavior.

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 0%, so the description carries the full burden, and it does not mention either parameter. The 'limit' parameter (default 50, max 200) is never explained, and 'buildingId' is only implicitly tied to 'a building' in the prerequisite sentence. With two undocumented parameters, this is a clear gap.

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 and resource ('List pending bank transactions') and adds distinctive scope: each transaction is returned with its 'best payment or expense match candidates'. That distinguishes it from plain listings like list_payments or list_expenses. It does not name the most relevant sibling, reconcile_transaction, so it stops short of full differentiation.

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?

The second sentence gives a real precondition: bank import tools only work when a building has bank sync configured. However, it does not say when to call this versus reconcile_transaction or how to follow up on the returned candidates, so the when-to-use guidance is implied rather than explicit.

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