Skip to main content
Glama

Taokeh MCP server

Bank reconciliation report

bank_reconciliation_report
Read-only

The AUDIT bank reconciliation for one bank account, exactly as Banking → Reconciliation report and Clear transactions show it — so you can work the reconciliation WITH the owner instead of sending them to the app. Returns (1) report: balance per bank statement (or "Not stated" when the statement carries no closing balance — pass balance from the paper statement to work it through; used for this answer only, never stored), less unpresented payments, add deposits not yet credited, adjust for statement lines not yet in the books, = balance per books worked from the statement, beside the ledger balance and the UNEXPLAINED difference (never forced to zero), plus the Clear Transaction listing for the statement period; (2) clearStep: the book entries not yet cleared up to the statement date (each with its entryId, date, reference, description, signed amount, and any suggested statement line of the same amount), and the statement lines a tick may pair with (statementLineId, date, amount, remaining); (3) hints: the three patterns the page explains, in the page's own words (explanation) — a pair of entries that cancel out (clearDate is never before the statement starts), a cash sale with no deposit on the statement (never counter-day or POS takings), and an opening balance the books do not hold: none on the account (kind: missing) or one dated after the first statement starts (kind: late), never given when the report ties; when actionable is false, no fix is safe to name, so name none. Pick the account with bankAccountId (default: the first bank account), and the statement with statementId (default: its latest) or a date with asOf. Clear transactions lists 300 rows at a time, oldest first; offset reads the next batch. Report lists over 200 rows are truncated, their totals never. Ringgit bank accounts only — a credit card or a foreign-currency account is refused with the page's own sentence. READ-ONLY: to tick entries, file create_bank_clearing_draft; to settle a posted payment against invoices or bills, file create_payment_match_draft. The owner approves both in Taokeh.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asOfNoReconcile to this date by hand instead of 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 statement carries none ("Not stated"). Never 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. Added

TDQS

A5/5.0
Behavior5/5

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

The description goes far beyond the annotations, disclosing read-only behavior, the 'never forced to zero' difference, handling of 'Not stated' balances, pagination limits, truncation behavior, and refusal of non-ringgit accounts. It aligns with the readOnlyHint annotation and adds substantial behavioral context.

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 description is long but every sentence is purposeful: it front-loads the core purpose, then systematically details return objects, edge cases, defaults, restrictions, and related tools. No fluff or redundancy; the structure aids comprehension.

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, the description must explain return values, which it does comprehensively (report, clearStep, hints) including their subfields and special conditions. It also covers pagination, defaults, and restrictions, making the tool fully usable without external reference.

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

Parameters5/5

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

Even though the schema describes all 5 parameters (100% coverage), the description enriches them: explains defaults (first bank account, latest statement), the purpose of balance (only when statement lacks closing balance, never stored), offset's paging (300 rows), and asOf's hand-reconciliation role. This adds significant meaning beyond the schema.

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 clearly states the tool's purpose: performing an audit bank reconciliation for one bank account, matching the app's behavior. It specifies the resource (bank account) and distinguishes from siblings like bank_reconciliation_status and create_bank_clearing_draft, leaving no ambiguity.

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

Usage Guidelines5/5

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

It explicitly explains when to use this tool (to work the reconciliation with the owner) and names alternative tools for actions (create_bank_clearing_draft for ticking entries, create_payment_match_draft for settling payments). It also details parameter defaults and selection logic, leaving no guesswork.

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