Skip to main content
Glama
Sign In
BankConv MCP server

BankConv MCP server

by wassim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Convert a bank statement PDF

convert_statement

Converts a PDF bank or credit card statement into JSON transactions or saves import-ready CSV, OFX, QFX, QBO, or Xero CSV files.

Instructions

Convert a PDF bank or credit card statement on this computer with BankConv. Use this for a new PDF; for a statement converted earlier, use get_transactions or download_statement with its conversion id (list_conversions finds it). With output "transactions" (the default) it returns a summary and every transaction as JSON: ISO date, description, signed amount (money in positive), running balance; opening balances and totals are left out. Any other output saves that file and returns only its path and any warnings. csv: the statement as a spreadsheet; ofx: Xero, Sage, MYOB, QuickBooks Online; qfx: Quicken; qbo: QuickBooks Desktop (Web Connect); xero: Xero CSV with Xero's own columns. Uploading uses one BankConv page per PDF page. Waits until the conversion finishes. Errors say what went wrong: not_found for an unknown conversion id, gone once a conversion was deleted under data retention (24 hours by default), unreadable_statement when the tables can't be read as transactions (the message names the row), insufficient_credits when the account has too few pages.

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": {
      "file_path": "<file_path>"
    },
    "name": "convert_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputNo"transactions" returns the rows to you; any other value saves that file. csv: the statement as a spreadsheet; ofx: Xero, Sage, MYOB, QuickBooks Online; qfx: Quicken; qbo: QuickBooks Desktop (Web Connect); xero: Xero CSV with Xero's own columns.transactions
save_toNoFor file outputs: a file path or folder. Defaults to the PDF's folder, named after the PDF. An existing file at that path is overwritten.
passwordNoThe PDF password, if the statement is password-protected.
file_pathYesPath to the PDF statement on this computer.
timeout_secondsNoHow long to wait for the conversion. On timeout the conversion keeps running; fetch it later with its conversion id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / save_to / description
      Previous value: -"For file outputs: a file path or folder. Defaults to the PDF's folder."New value: +"For file outputs: a file path or folder. Defaults to the PDF's folder, named after the PDF. An existing file at that path is overwritten."
    • changedInput schema / properties / timeout_seconds / description
      Previous value: -"How long to wait for the conversion."New value: +"How long to wait for the conversion. On timeout the conversion keeps running; fetch it later with its conversion id."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, but the description does not mention that save_to overwrites an existing file — that destructive side effect is disclosed only in the input schema, and nothing in the description acknowledges it. On the other hand, the description does add genuinely behavioral context the annotations cannot convey: it blocks until the conversion finishes, and it bills one BankConv page per PDF page. The pagination cost is useful, but the gap on the overwrite risk against a false destructiveHint keeps this at 3.

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?

It is front-loaded with purpose and sibling routing before the output-mode list, and there is no filler. It is a long, dense block of comma-spliced clauses, but each sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain return values — and it does, naming the returned fields and the saved-file path plus warnings for file outputs. But it never says what the returned 'summary' contains, and it omits the overwrite behavior of save_to. Good coverage of errors and timing, with a real gap in the default-return shape.

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 coverage is 100%, so the description's recap of output modes largely restates what the enum description already says. What it does add — that output="transactions" returns structured JSON, that every other value saves a file — is real semantics, but the save_to, password and timeout_seconds parameters are left entirely to the schema. With the schema doing the heavy lifting, a 3 is fair.

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 ('Convert a PDF bank or credit card statement on this computer with BankConv') and immediately distinguishes itself from the siblings that handle already-converted statements.

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 says to use this tool for a new PDF and to use get_transactions or download_statement with a conversion id for one converted earlier, naming list_conversions as the way to find that id. The when-not path and the alternatives are both spelled out.

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

Deploy Server

Other Tools