Skip to main content
Glama

reconcile_bank_act

One action on one open bank movement (ZEN-2), with its row's version: accept its held proposal, ignore it, skip / unskip. Ignore and skip need a reason; recorded with your user. Link and settle through the row's operations. Returns the new status.

On this MCP surface a null argument means "not provided": it is dropped before the request is sent, exactly as if the field were omitted.

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": {
      "company_id": "<company_id>",
      "decision_id": "<decision_id>",
      "action": "<action>",
      "version": "<version>"
    },
    "name": "reconcile_bank_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
reasonNo
versionYes
company_idYes
decision_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It discloses that a reason is recorded with the user, that a row version is required, and that the tool returns a new status, plus null-argument handling, but it omits permissions, reversibility/destructiveness, and what the undocumented enum actions such as delete or reject do.

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 paragraphs, front-loaded with the core action and scoped by the row version. The null-argument note is a general MCP caveat but remains relevant and does not bloat the description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with five parameters, an enum, and no output schema or annotations, the description leaves too much unsaid: two required IDs and most action semantics are absent. The return-value note is present, but overall it is not complete enough for safe invocation.

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 coverage is 0%, so the description must explain all five parameters. It explains version and reason and partially maps action values, but omits company_id, decision_id, and most enum options including delete and reject.

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 it performs one action on one open bank movement and enumerates accept/ignore/skip/unskip, so the resource and operation are identifiable. It does not distinguish this from siblings such as accept_autopost_decision or call_operation, so it stops short of 5.

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?

Gives action-level guidance that ignore and skip need a reason, and routes link/settle work to the row's operations, which implies usage. But it never states when to choose accept versus ignore versus skip, or when to use this tool instead of a sibling operations tool.

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