Skip to main content
Glama

Zovo Bank Reconciliation

Reconcile bank to books

reconcile_bank_to_books

Use this when the user attaches a bank export or statement AND their books (cash account register or general ledger export from accounting software or a spreadsheet) and wants a bank reconciliation: "reconcile my bank statement", "reconcile bank statement against my books", "list what doesn't match", "find outstanding checks and deposits in transit", "match bank transactions to the ledger". Matches rows by check number, amount and date (with a date window), and sums (one deposit = several invoices); lists all unmatched rows on both sides with a classification (outstanding check, deposit in transit, bank fee, interest, NSF, likely duplicate, likely amount typo); builds adjusted bank vs adjusted book balance (PASS only at $0.00); returns an Excel workbook and a PDF reconciliation statement. Does not connect to bank accounts or accounting software, does not post entries, and is not for a single statement without books (use a statement converter for that). 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>"
    },
    "name": "reconcile_bank_to_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
bank_fileYesThe bank side: the bank's CSV or Excel (.xlsx) transaction export, or a text PDF bank statement, e.g. bank-september.csv.
books_fileYesThe 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_signNoSign 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_orderNoOrder 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_endNoStatement / 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_columnsNoOptional column names for the bank file when auto-detection picks the wrong column, e.g. {"date":"Post Date","amount":"Amount"}.
books_columnsNoOptional column names for the books file, e.g. {"date":"Date","debit":"Debit","credit":"Credit","check_no":"Num"}.
max_group_sizeNoMost rows combined when one deposit equals several book entries (or the reverse), e.g. 4 (default).
check_clear_daysNoDays 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_daysNoDays a bank posting may differ from the book date and still match the same amount, e.g. 5 (default).
bank_ending_balanceNoEnding balance on the bank statement at period end, in dollars, e.g. 48210.55. With book_ending_balance this gives the full adjusted-balance reconciliation.
book_ending_balanceNoCash account balance in the books at period end, in dollars, e.g. 51022.10.

Output Schema

NameRequiredDescriptionDefault
modeYes
noteYes
filesYes
countsYes
statusYesPASS only when both ending balances are known and the difference is $0.00; BALANCES_NEEDED = activity explained, balances needed.
warningsYes
downloadsYes
period_endYes
explanationYes
top_bank_onlyYes
top_book_onlyYes
reconciliationYes
bank_only_by_classYes
book_only_by_classYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), it discloses that each call writes new Excel and PDF files held privately for one hour and then deleted — which explains the non-idempotent hint and the artifact lifecycle. It also gives hard limits (20,000 rows per file, 2,000,000-cell cap for CSV/text), the PASS gate at $0.00, and that it neither connects to bank/accounting systems nor posts entries. No contradiction with annotations.

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 trigger condition and matching logic, and every later sentence carries real information (limits, file lifecycle, exclusion). The dense run of quoted example utterances and semicolon-chained clauses makes it slightly bloated for a single paragraph.

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, nested-object tool with an output schema, this covers the essentials: inputs required, matching behavior, limits, artifacts produced, and what it will not do. Return values are summarized and then detailed by the output schema, so nothing an agent needs to invoke it correctly is missing.

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 baseline is 3; the description rises above it by explaining the matching semantics behind the tuning parameters — the date window for same-amount matches, the check-clear span, and grouping for one-deposit-to-many-entries. It never explicitly ties names like date_window_days or books_sign to their behavior, so it stops short of a 5.

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 precise verb+resource ('bank reconciliation') and then enumerates the exact mechanics: matching by check number, amount and date window, summing one deposit to several invoices, classifying unmatched rows, and building adjusted bank vs adjusted book balances. An agent can tell this apart from the sibling explain_reconciliation_difference without inspecting any schema.

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 states the triggering condition explicitly (a bank export AND books attached), gives sample user phrasings, and names the exclusion case plus the alternative ('not for a single statement without books — use a statement converter'). Both when-to-use and when-not-to-use are covered.

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