Zovo Bank Reconciliation

Explain reconciliation difference

explain_reconciliation_difference

Use this when the user attaches the bank file and the books file, gives the bank statement ending balance and the book balance, and asks why the bank reconciliation does not balance: "why is my bank reconciliation off", "reconciliation difference", "find the difference between bank and books". Runs the same matching, computes adjusted bank vs adjusted book balance, and finds the smallest set of listed items (up to 4) whose amounts account for the difference, plus checks for a reversed sign, a transposition (difference divisible by 9) and a row with that same amount. Returns the same Excel and PDF downloads. Does not change any file and does not find items that are missing from both files. Supports up to 20,000 rows per file; CSV and text tables have a 2,000,000-cell limit (including empty cells). Each call saves new Excel and PDF files on the plugin server for 1 hour (private download links), then deletes them.

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_file": "<bank_file>",
      "books_file": "<books_file>",
      "bank_ending_balance": "<bank_ending_balance>",
      "book_ending_balance": "<book_ending_balance>"
    },
    "name": "explain_reconciliation_difference"
  }
}

Input Schema

Name	Required	Description
`bank_file`	Yes	The bank side: the bank's CSV or Excel (.xlsx) transaction export, or a text PDF bank statement, e.g. bank-september.csv.
`books_file`	Yes	The book side: the cash/bank account register or general ledger export from accounting software or a spreadsheet (CSV or .xlsx), e.g. books-september.xlsx.
`books_sign`	No	Sign of the books file amounts: auto (default) flips only when the amounts clearly match the bank with the opposite sign; as_written keeps them; flip reverses them. Example: auto.
`date_order`	No	Order of numeric dates in both files: MDY (US, 09/02/2026) or DMY (02/09/2026). Detected per file when a day is above 12; US is assumed otherwise.
`period_end`	No	Statement / period end date YYYY-MM-DD, e.g. 2026-09-30. Default: the statement end on a PDF, else the month end of the last book entry (capped by the bank file).
`bank_columns`	No	Optional column names for the bank file when auto-detection picks the wrong column, e.g. {"date":"Post Date","amount":"Amount"}.
`books_columns`	No	Optional column names for the books file, e.g. {"date":"Date","debit":"Debit","credit":"Credit","check_no":"Num"}.
`max_group_size`	No	Most rows combined when one deposit equals several book entries (or the reverse), e.g. 4 (default).
`check_clear_days`	No	Days a check may take to clear and still match by amount, e.g. 60 (default). Matches by check number allow the same span.
`date_window_days`	No	Days a bank posting may differ from the book date and still match the same amount, e.g. 5 (default).
`bank_ending_balance`	Yes	Ending balance on the bank statement at period end, in dollars, e.g. 48210.55.
`book_ending_balance`	Yes	Cash account balance in the books at period end, in dollars, e.g. 51022.10.

Output Schema

Name	Required	Description
`mode`	Yes
`note`	Yes
`files`	Yes
`counts`	Yes
`status`	Yes	PASS only when both ending balances are known and the difference is $0.00; BALANCES_NEEDED = activity explained, balances needed.
`warnings`	Yes
`downloads`	Yes
`period_end`	Yes
`explanation`	Yes
`top_bank_only`	Yes
`top_book_only`	Yes
`reconciliation`	Yes
`bank_only_by_class`	Yes
`book_only_by_class`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: it does not modify the input files, it creates new Excel and PDF files on the plugin server with private links that expire after 1 hour, and it enforces limits of 20,000 rows per file and 2,000,000 cells for CSV/text. This also explains why readOnlyHint is false despite 'does not change any file' — the side effect is temporary server artifacts, not edits to user data.

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?

Front-loaded with the usage trigger and examples, then moves through mechanism, outputs, exclusions, and limits in a logical order. It is dense but nearly every clause carries information; the phrase 'the same matching' and 'the same Excel and PDF downloads' is slightly opaque without naming the sibling tool.

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?

For a 12-parameter tool with nested file objects, an output schema, and no destructive semantics, the description covers the trigger, diagnostic logic, side effects, retention, and hard input limits. Nothing an agent needs to decide to call it, or to warn the user about file-size constraints, is missing.

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 100%, so every parameter, enum, and default is already documented in the schema; the description only alludes to the 'up to 4' grouping that maps to max_group_size. It adds no new guidance on books_sign, date_order, column overrides, or the matching windows, so baseline 3 applies.

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?

States a specific verb and resource ('explain why the bank reconciliation does not balance') and spells out the mechanism: same matching, adjusted bank vs adjusted book balance, smallest set of up to 4 items, sign flip, transposition rule, and same-amount row check. An agent can distinguish it from reconcile_bank_to_books because this one is diagnostic (explains the residual difference) rather than producing the reconciliation itself.

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?

Gives an explicit trigger condition (both files attached, both ending balances supplied, user asks why it is off) backed by three example phrasings, plus one clear exclusion ('does not find items that are missing from both files'). It never names the sibling reconcile_bank_to_books as the alternative for a plain reconciliation, so the when-not-to-use routing is only implied.

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

All Zovo Bank Reconciliation tools Inspect

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

Need Help?