Skip to main content
Glama

Binyan.im · בניינים

Unmatch bank transaction

unmatch_bank_transaction
Destructive

Undo a bank transaction match: removes its allocations and returns the transaction to pending so the match can be redone. The payment or expense itself is not changed; edit it separately if needed. The action is audit logged. 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>"
    },
    "name": "unmatch_bank_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildingIdYes
transactionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only say destructive=true and idempotent=false; the description adds the substance an agent actually needs: exactly what is destroyed (allocations), the resulting state (pending), what is explicitly untouched (the payment/expense), and that the action is audit logged. The bank-sync precondition is additional operational context not present in any structured field.

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?

The core action and its effect are front-loaded in the first sentence, followed by the important non-effect, the audit note, and the availability caveat — each sentence carries distinct information. Slightly more could be trimmed, but nothing is redundant.

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 destructive two-parameter mutation with no output schema, the description covers effect, non-effect, audit logging, and a preconditions. Remaining gaps are what happens if the transaction is not currently matched (error vs no-op) and any permission requirement, which matters given idempotentHint=false.

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% and the description says nothing about buildingId or transactionId — no scoping rules, no format hints, no note that the transaction must currently be matched. The parameter names are largely self-explanatory, but the description makes no attempt to compensate for the documentation 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+resource ("Undo a bank transaction match") and immediately enumerates the effect: allocations removed, transaction returned to pending. That makes the operation distinguishable from reconcile_transaction by implication, but it never names or contrasts a sibling explicitly, which keeps it out of the top band.

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?

Usage context is clear ("so the match can be redone") and a real precondition is stated: bank import tools only work when a building has bank sync configured. There is no explicit when-not-to-use guidance or named alternative for the redo path, so it stops short of a 5.

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