Skip to main content
Glama
Sign In

Taokeh MCP server

by my.taokeh
OverviewDiscussionsAdmin

Bank reconciliation status

bank_reconciliation_status
Read-only

Where each bank account stands on reconciliation: GL balance vs the latest statement's closing (with the difference, or an honest "unknown" when no balance is stated); rowCounts by stored status (SUGGESTED = proposed, awaiting the owner; UNCATEGORIZED = never categorised, incl. hand-typed rows; CONFIRMED = categorised, not in the ledger; POSTED; IGNORED = set aside); the unreviewed backlog (SUGGESTED + UNCATEGORIZED not paired on Clear transactions) with pairedInBooks; reconcilingItems — each item's signed effect on the difference, summing to it exactly (NOT_EXPLAINED is the honest remainder, STATEMENTS_DONT_JOIN a missing or duplicated statement). A statement line PAIRED on Clear transactions is in the books: it and the entry it is paired with sit in no other item, and PAIRED_ON_CLEAR appears only when a pair is for a different amount (its effect is what the pair leaves; pairedOnClear gives the paired line count). Cash moved with no bank line is DRIFT_: DRIFT_EXPENSE, DRIFT_GATEWAY_PAYOUT, DRIFT_OPENING, DRIFT_MANUAL, DRIFT_CASH_SALE (cash sales booked to the account), DRIFT_CASH_BILL (bills paid in cash), DRIFT_LOAN (loan instalments), DRIFT_DOCUMENT (other records: payroll, assets, credit notes, adjustments…), and DRIFT_OTHER only for what cannot be attributed; notOnStatementNotInBooks — unposted lines on no statement (hand-typed, or a recorded receipt/payment not yet posted), which do not affect the difference; and per recent statement its balances, tie-out and counts (paired = lines paired on Clear transactions, never counted as suggested, confirmed or uncategorized; pairsLeaving = that statement's pairs for a different amount and what they leave). A CREDIT CARD's figures are a liability: negative = money OWED, never cash. Same figures as the in-app Bank Reconciliation page. READ-ONLY.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, and the description reinforces it with 'READ-ONLY.' Beyond that it adds real behavioral context: it defines what each stored status means, explains pairing semantics, and states the figures match the in-app page. It does not cover auth requirements or performance, so not a 5.

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

Conciseness2/5

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

The description is a single enormous run-on paragraph packed with parentheticals and nested definitions. It is front-loaded with the main purpose, but the volume and lack of structure make it hard to scan and violates the conciseness bar.

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?

With no output schema, the description must and does explain return contents in detail (rowCounts, reconcilingItems, drift categories, per-statement tie-outs). It is arguably over-complete rather than under-complete, which is the right side of the tradeoff for a schema-less tool.

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?

There are zero parameters, so the baseline is 4; there is nothing for the description to clarify or compensate for.

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 opening clause ('Where each bank account stands on reconciliation: GL balance vs the latest statement's closing') states a specific verb/resource/scope clearly. It does not, however, explicitly differentiate itself from siblings like bank_reconciliation_report or bank_review_queue, so an agent must infer the boundary.

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 statement and no named alternatives, even though several siblings (bank_reconciliation_report, bank_review_queue, bank_reconciliation_status) clearly overlap. The agent gets a rich payload description but no routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Taokeh MCP server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources