Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Match bank lines to ledger entries

accounting-schedules_bank-reconciliation-match
Read-onlyIdempotent

Match bank statement lines to ledger entries by amount+reference, amount+date tolerance, and optional many-to-one subset sums. Price $0.04 USDC. POST /api/v1/accounting-schedules/bank-reconciliation-match. An unpaid call returns the x402 payment terms and does not run.

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>",
      "ledger": "<ledger>"
    },
    "name": "accounting-schedules_bank-reconciliation-match"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankYesbank, array. Required.
ledgerYesledger, array. Required.
allowManyToOneNoallowManyToOne, boolean. Required.
dateToleranceDaysNodateToleranceDays, integer, from 0 to 90. Required.

Output Schema

NameRequiredDescriptionDefault
matchesNomatches. Array.
sourcesNosources. Array.
differenceNodifference. Number.
limitationsNolimitations. Array.
unmatchedBankNounmatchedBank. Array.
unmatchedLedgerNounmatchedLedger. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses two operationally critical behaviors: the price ($0.04 USDC) and that an unpaid call returns x402 payment terms without executing. Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so this is genuine added context rather than repetition. It does not explain tie-breaking between multiple candidate matches or how unmatched lines are reported.

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?

Three short, front-loaded sentences: capability first, then cost, then endpoint and payment-gating behavior. Nothing is padded, and the operational details (price, POST path, x402) each carry distinct information an agent needs before invoking.

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?

An output schema exists, so return-value explanation is not required, and the description plus rich nested schema are sufficient to construct a call. The remaining gap is decision-level: no statement about match ambiguity, unmatched-line handling, or what the boolean default of allowManyToOne implies in practice.

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 coverage is 100%, so the schema already documents all four parameters, making 3 the baseline. The description does add modest interpretive value by mapping date tolerance and many-to-one subset sums onto the matching behavior driven by dateToleranceDays and allowManyToOne, but it gives no units, defaults, or range guidance of its own.

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 ('Match bank statement lines to ledger entries') and enumerates the matching strategies supported: amount+reference, amount+date tolerance, and many-to-one subset sums. No sibling tool in the catalog performs matching, so an agent will not confuse it, though the description never explicitly contrasts itself with the schedule-generation siblings.

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 description implies usage (supply bank and ledger arrays and the tool reconciles them) and names the three matching modes, but it never says which mode is applied when, whether modes are tried in precedence order, or when an agent should set allowManyToOne. With no comparable alternative tool, that is implied guidance rather than explicit when/when-not rules.

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