Skip to main content
Glama

Bank and Book Reconciliation

bpj_bank_book_reconciliation
Read-onlyIdempotent

Adjust the statement and book for deposits in transit, checks, fees and interest and quantify the remaining difference.

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": {
      "bank": "<bank>",
      "deposits": "<deposits>",
      "checks": "<checks>",
      "ledger": "<ledger>",
      "fees": "<fees>",
      "earned": "<earned>"
    },
    "name": "bpj_bank_book_reconciliation"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankYes
feesYes
checksYes
earnedYes
ledgerYes
depositsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety behavior is largely covered. The description adds that the tool applies deposits-in-transit, outstanding-check, fee, and interest adjustments and quantifies the remaining difference, but it does not clarify whether adjusted balances are returned or how the difference is structured.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no redundant wording. Every clause maps directly to an input category or the output concept of the remaining difference.

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?

With six required parameters and no output schema, the description should clarify return values and the reconciliation formula. It states that the tool quantifies the remaining difference but leaves the adjusted balances and output structure unspecified.

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?

Schema description coverage is 0%, but the schema titles label all six required inputs. The description compensates by mapping statement/book and deposits/checks/fees/interest to the inputs, though it does not specify sign conventions, such as whether checks and fees reduce the balance.

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 states a specific accounting action (adjust statement and book for deposits in transit, checks, fees and interest) and a result (quantify the remaining difference). The bank/book framing distinguishes it from other reconciliation siblings such as EBITDA or headcount reconciliation, though it does not explicitly name alternatives.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no comparison to sibling reconciliation tools. Usage is only implied by the tool name and the reconciliation language in the description.

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.