Tallyproof Bank Statements

Summarize transactions

summarize_transactions

Read-only

Use this when the user pastes or lists bank or credit card transactions (date, description, amount) and wants them reconciled, totaled by month or category, or exported: "does my statement balance", "money in and out by month", "categorize these transactions", "make a QuickBooks CSV from these". Checks opening + transactions = closing to the cent and the running balance row by row, points to the rows that break it, suggests categories, and returns Excel, CSV and QuickBooks CSV downloads. Do not use when a statement file is attached (use convert_bank_statement); does not give tax or accounting advice.

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": {
      "transactions": "<transactions>"
    },
    "name": "summarize_transactions"
  }
}

Input Schema

Name	Required	Description
`account_type`	No	auto (default): a PDF is classified from its text; pasted rows and CSV/Excel exports count as bank unless the balances or the sign pattern show a credit card (the result says so). bank: checking or savings. credit_card: charges are money out and the statement shows a previous and new balance owed. Example: credit_card.
`transactions`	Yes	The transactions in statement order, e.g. [{"date":"2026-09-02","description":"PAYROLL ACME INC","amount":2450}, {"date":"2026-09-03","description":"GREENLEAF MARKET","amount":-82.17}].
`statement_year`	No	Closing year of the statement, used for dates printed without a year when the period is not on the file, e.g. 2026 (a December-January statement uses the January year).
`closing_balance`	No	Closing (ending or new) balance in dollars, e.g. 5034.47. Used with opening_balance to prove the total to the cent.
`opening_balance`	No	Opening (beginning or previous) balance in dollars, e.g. 4123.55. Only needed when the file has none, such as a CSV export without a balance column, or to override.

Output Schema

Name	Required	Description
`note`	Yes
`months`	Yes
`period`	Yes
`source`	Yes
`account`	Yes
`preview`	Yes
`warnings`	Yes
`downloads`	Yes
`categories`	Yes	Suggested categories from keyword rules; review before filing.
`transactions`	Yes
`reconciliation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint, non-destructive, closed-world), but the description adds real behavioral substance: it verifies opening + transactions = closing to the cent, checks the running balance row by row, identifies offending rows, and suggests categories. It does not quantify limits (e.g., 5000-row cap is only in schema) or cost/latency, so it falls just short of full marks.

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?

A single dense paragraph that is well front-loaded: trigger and example phrases first, then behavior, then exclusions. The clause listing output formats (Excel, CSV, QuickBooks CSV) is somewhat redundant given the output schema, but nothing else is wasted.

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?

Read-only tool with a full output schema, 100% parameter documentation, explicit sibling routing, and stated scope exclusions. An agent has everything needed to decide to call it and how to shape the input, plus the behavioral guarantees of reconciliation.

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% and every parameter has a detailed inline description including an enum explanation for account_type, so the schema does the heavy lifting. The description only gestures at the input shape ('date, description, amount'), adding no format or sign-convention guidance beyond what the schema already states.

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+resource (summarize/reconcile transactions) plus the concrete operations performed: totaling by month or category, balance checking, categorization, and export. It explicitly contrasts with the sibling convert_bank_statement, so an agent can route without opening either 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?

Front-loads the trigger condition ('user pastes or lists bank or credit card transactions') with four quoted example utterances, then names the exclusion ('Do not use when a statement file is attached (use convert_bank_statement)') and an additional scope limit (no tax or accounting advice). Both when-to-use and when-not are explicit.

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

All Tallyproof Bank Statements 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?