bankstatementparser-mcp

Summarize statement balances

summarize_statement

Read-onlyIdempotent

Summarize an inline statement's balances and totals only.

Instructions

Summarize an inline statement's balances and totals only.

Use this when you need just the opening/closing balances, currency, and
other summary fields without the per-transaction rows. For the full
transaction detail alongside the summary, use ``parse_statement``
instead.

Args:
    content: The raw statement text.
    filename: Original filename; its extension selects the format.
    format: Explicit format override.

Returns:
    The summary record with Decimal values stringified.

Raises:
    ToolError: If the format is unsupported, cannot be detected, or
        the payload does not parse.

Input Schema

Name	Required	Description	Default
`format`	No	Explicit format identifier that overrides detection from the filename. Must be exactly one of: 'camt', 'pain001', 'csv', 'ofx', 'qfx', 'mt940' (see list_supported_formats). When omitted, the format is inferred from the filename extension.
`content`	Yes	The raw statement text to summarize, inline (not a file path). Accepts ISO 20022 CAMT.053 and pain.001 XML, SWIFT MT940, CSV exports, and OFX/QFX payloads.
`filename`	No	Original filename of the payload; its extension (.xml, .csv, .ofx, .qfx, .mt940, .sta) selects the format when 'format' is omitted. Defaults to 'statement.xml'.	statement.xml

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.0.19Sep 1, 2026

changedInput schema / properties / format / description

Previous value: -"Explicit format identifier that overrides detection from the filename. Must be exactly one of: 'camt', 'csv', 'mt940', 'ofx', 'pain001', 'qfx' (see list_supported_formats). When omitted, the format is inferred from the filename extension."New value: +"Explicit format identifier that overrides detection from the filename. Must be exactly one of: 'camt', 'pain001', 'csv', 'ofx', 'qfx', 'mt940' (see list_supported_formats). When omitted, the format is inferred from the filename extension."

changedInput schema / properties / format / enum

Previous value: -[
-  "camt",
-  "csv",
-  "mt940",
-  "ofx",
-  "pain001",
-  "qfx"
-]New value: +[
+  "camt",
+  "pain001",
+  "csv",
+  "ofx",
+  "qfx",
+  "mt940"
+]

Changed2 schema fields changedJul 29, 2026

changedInput schema / properties / format / description

Previous value: -"Explicit format identifier that overrides detection from the filename. One of: 'camt' (CAMT.053), 'pain001', 'csv', 'ofx', 'qfx', 'mt940'. When omitted, the format is inferred from the filename extension."New value: +"Explicit format identifier that overrides detection from the filename. Must be exactly one of: 'camt', 'csv', 'mt940', 'ofx', 'pain001', 'qfx' (see list_supported_formats). When omitted, the format is inferred from the filename extension."

addedInput schema / properties / format / enum

Added value: +[
+  "camt",
+  "csv",
+  "mt940",
+  "ofx",
+  "pain001",
+  "qfx"
+]

Changed3 schema fields changedv0.0.16Jul 10, 2026

addedInput schema / properties / content / description

Added value: +"The raw statement text to summarize, inline (not a file path). Accepts ISO 20022 CAMT.053 and pain.001 XML, SWIFT MT940, CSV exports, and OFX/QFX payloads."

addedInput schema / properties / filename / description

Added value: +"Original filename of the payload; its extension (.xml, .csv, .ofx, .qfx, .mt940, .sta) selects the format when 'format' is omitted. Defaults to 'statement.xml'."

addedInput schema / properties / format / description

Added value: +"Explicit format identifier that overrides detection from the filename. One of: 'camt' (CAMT.053), 'pain001', 'csv', 'ofx', 'qfx', 'mt940'. When omitted, the format is inferred from the filename extension."

First observedv0.0.14Jul 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds value beyond that by disclosing the failure mode (ToolError on unsupported/undetectable format or unparseable payload) and a real output quirk (Decimal values stringified), which the agent would otherwise not anticipate.

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?

Well front-loaded: the scope statement and the sibling routing come first, before the docstring-style Args/Returns/Raises blocks. The Returns line is mildly redundant given an output schema exists, but no sentence 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?

For a read-only, single-payload parser with a documented schema and output schema, the definition covers everything needed to invoke it correctly: scope, format detection precedence (filename extension vs explicit override), the alternative tool, and the error conditions.

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 the baseline is 3. The Args block largely restates the schema ('content: The raw statement text', 'filename: Original filename; its extension selects the format', 'format: Explicit format override') without adding syntax or precedence detail beyond what the schema already says.

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 ('Summarize an inline statement's balances and totals only') and immediately bounds the scope with 'only', which is exactly the differentiator from the sibling parse_statement. An agent can tell the two apart 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?

Explicitly states when to use it ('when you need just the opening/closing balances, currency, and other summary fields without the per-transaction rows') and names the alternative plus the condition that selects it ('For the full transaction detail alongside the summary, use parse_statement instead'). Nothing is left to inference.

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

Deploy Server