Convert MT940 to Excel and CSV, and check that each bank statement adds up.
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between tools. The tool's scope is clearly stated and self-contained.
The single name convert_mt940_statement follows a clear verb_noun pattern with snake_case, and correctly signals both the action and the file format.
One tool is the natural minimum for a single-purpose converter, but it is a thin surface: input parsing, conversion, and balance validation are all folded into a single call with no granular options.
The tool covers the core lifecycle of the domain: read MT940/camt.05x, emit Excel plus CSV, and validate balances to the cent. Minor gaps exist (no control over output format variants or per-file error reporting, and PDF/CSV inputs are explicitly excluded), but agents can work around these.
Use this when the user wants to convert an MT940 file to Excel or CSV ("mt940 to excel", "mt940 converter", "convert mt940 to csv", "camt 053 to excel", "camt.053 converter") or check that a bank statement file adds up. Reads SWIFT MT940 (.sta, .mt940, .txt) or ISO 20022 camt.053 / camt.052 / camt.054 XML from the attached file or pasted text, and returns an Excel workbook (Transactions sheet with booking date, value date, signed amount, debit, credit, running balance, counterparty, description, references; Balance check sheet) and a CSV. Checks opening + credits - debits = closing for each statement to the cent and shows any difference. Does not read PDF or CSV statements, does not categorize transactions, and does not send data to a bank.
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | The bank statement file: MT940 (.sta, .mt940, .940, .txt) or camt.053 / camt.052 / camt.054 XML, e.g. statement.sta or camt053.xml. | |
| statement_text | No | The MT940 or camt XML text when it was pasted instead of attached, e.g. ":20:STMT1\n:25:NL91ABNA0417164300\n:28C:1/1\n:60F:C261001EUR1000,00\n:61:2610021002D25,50NTRFNONREF\n:86:Coffee\n:62F:C261002EUR974,50". |
| Name | Required | Description |
|---|---|---|
| notes | Yes | |
| format | Yes | |
| issues | Yes | |
| preview | Yes | |
| downloads | Yes | |
| file_name | Yes | |
| mismatches | Yes | |
| statements | Yes | |
| not_checked | Yes | |
| transactions | Yes | |
| balance_check | Yes | |
| preview_count | No | |
| statements_count | No | |
| flagged_transactions | Yes | |
| links_expire_minutes | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this read-only, idempotent, non-destructive and closed-world, and the description still adds real behavior: it returns a Transactions sheet with named columns plus a Balance check sheet and a CSV, and it reconciles opening + credits - debits = closing to the cent. The privacy note ('does not send data to a bank') and the input-format limits are exactly the kind of context annotations cannot carry.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the use case, then input formats, then outputs, then exclusions — a logical order with no filler sentences. The long run of quoted trigger phrases is slightly verbose, though it serves routing rather than padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-input, file-plus-text tool with an output schema, the description covers formats, outputs, and reconciliation behavior thoroughly. The one residual gap is that it never says one of file/statement_text is mandatory, which matters since the schema marks nothing required.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3; the description earns an increment by explaining that input arrives either as an attached file or as pasted text, which tells the agent the two parameters are alternative input modes. It does not state precedence or that at least one must be supplied, which keeps it below a 5.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb plus resources: converts MT940 (.sta, .mt940, .txt) and ISO 20022 camt.053/.052/.054 into an Excel workbook and CSV, and additionally verifies statement totals. The scope is precise enough that an agent could not confuse it with a generic file or finance tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Opens with an explicit when-to-use trigger ('the user wants to convert an MT940 file to Excel or CSV') and lists the literal phrases that should route here ('mt940 to excel', 'camt 053 to excel'). It also names exclusions — no PDF/CSV statements, no transaction categorization, no data sent to a bank — so misfires are easy to avoid.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
convert_mt940_statementConvert PDF bank statements to checked Excel, CSV or JSON with balance validation.
Convert bank statement PDFs to Excel, CSV, OFX or QBO, every row checked against the balances.
Convert PDF bank statements into Excel and check that the balances add up. Invoices and tables too.
Normalize bank statements (CSV, camt, MT940, OFX, QIF) to JSON, analyze, export.
Add one secure layer between your agents and this server.
