Skip to main content
Glama

Taokeh MCP server

Bank reconciliation report

bank_reconciliation_report
Read-only

The audit bank reconciliation for one bank account, as Banking → Reconciliation report and Clear transactions show it. Returns (1) report: balance per bank statement ("Not stated" when the statement has none; balance supplies it for this answer only), less unpresented payments, plus deposits not yet credited, adjusted for statement lines not yet in the books, giving the balance per books worked from the statement, beside the ledger balance and the unexplained difference (never forced to zero), setAsideLinesOnAnotherStatement {count, total} (set-aside lines not counted because another statement of the account also shows them), plus the Clear Transaction listing for the period; (2) clearStep: book entries not yet cleared up to the statement date (entryId, date, reference, description, signed amount, any same-amount statement line), and the statement lines a tick may pair with (statementLineId, date, amount, remaining); (3) hints: the page's three explained patterns (explanation): a pair of entries that cancel out, a cash sale with no deposit on the statement, and a missing (kind: missing) or late (kind: late) opening balance; when actionable is false, no fix is safe. Clear transactions lists 300 rows at a time, oldest first; report lists over 200 rows are truncated, their totals never. Ringgit bank accounts only; a credit card or foreign-currency account is refused. Read-only. Ticks are filed by create_bank_clearing_draft and settlements of a posted payment by create_payment_match_draft; the owner approves both in Taokeh.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bank_reconciliation_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoReconcile to this date without a statement, `YYYY-MM-DD`.
offsetNoClear transactions paging: skip this many uncleared rows (the page shows 300 at a time).
balanceNoThe closing balance printed on the paper statement, used only when the imported statement has none ("Not stated"). It is not stored.
statementIdNoAn imported statement — from `statements`. Omit for the latest (or give asOf instead).
bankAccountIdNoThe bank account — from `bankAccounts` in an earlier answer. Omit for the first bank account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / asOf / description
      Previous value: -"Reconcile to this date by hand instead of a statement (YYYY-MM-DD)."New value: +"Reconcile to this date without a statement, `YYYY-MM-DD`."
    • changedInput schema / properties / balance / description
      Previous value: -"The closing balance printed on the paper statement — used only when the statement carries none (\"Not stated\"). Never stored."New value: +"The closing balance printed on the paper statement, used only when the imported statement has none (\"Not stated\"). It is not stored."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes far beyond by disclosing the unexplained difference is never forced to zero, that set-aside lines on another statement are excluded and totalled, that `actionable: false` means no fix is safe, and that report rows truncate past 200 while totals never do. The "Not stated" handling for balance and the account-type refusal are behavioral caveats an agent could not infer from the annotations.

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

Conciseness3/5

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

It is front-loaded with the three return sections numbered, which helps, but the prose is a single dense run-on with heavy nested parentheticals that slows scanning. Given there is no output schema, most of the length is earned; the phrasing itself could still be tightened.

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

Completeness5/5

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

With no output schema and five optional parameters, the description carries the full burden and does so thoroughly — it documents each returned field group, the truncation and paging limits, edge cases like a missing balance or non-actionable hints, and the account-type restriction. An agent has everything needed to call it and interpret the result without further sources.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: `balance` supplies a statement-less figure for that answer only and is not stored, and `asOf` versus `statementId` are framed as mutually substitutable with defaults when omitted. Paging via `offset` at 300 rows is restated coherently with the clear-transaction listing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource+scope: the audit bank reconciliation for a single bank account, mirroring the Banking → Reconciliation report and Clear transactions views. It then enumerates exactly what comes back (`report`, `clearStep`, `hints`), so an agent can tell it apart from sibling reporting tools without opening the schema.

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 conditions are unusually explicit: read-only, Ringgit bank accounts only, credit-card and foreign-currency accounts refused, plus the note that ticks are filed by create_bank_clearing_draft and settlements by create_payment_match_draft with owner approval in Taokeh — a clear routing of write intent to siblings. What is absent is a direct comparison against the closely named bank_reconciliation_status sibling, so the when-to-use framing is strong but not exhaustive.

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