Skip to main content
Glama

upload_bank_statement

Import a BANK STATEMENT. CAMT.053 XML books at once; PDF, CSV, .xlsx queue (list_bank_statement_imports); .zip splits; legacy .xls, UTF-16 CSV refused. CSV/.xlsx imports only if opening + lines = closing, else nothing; with no printed opening/closing balance it fails until the person's balances per balances_needed (and the account if no IBAN) come via assign_bank_statement_import_accounts. file_base64: raw bytes, base64.

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": {
      "company_id": "<company_id>",
      "filename": "<filename>",
      "file_base64": "<file_base64>"
    },
    "name": "upload_bank_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
company_idYes
file_base64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose meaningful behavior: synchronous booking for CAMT.053 versus asynchronous queueing for other formats, zip extraction, rejected formats, and the silent no-op on an unbalanced CSV/.xlsx. It does not mention permissions, idempotency/duplicate handling, or what happens to an already-imported file.

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 core action and dense with useful detail; no filler sentences. The telegraphic style (parenthetical tool references, semicolon-chained clauses) makes it harder to parse than it needs to be.

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

Completeness4/5

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

No output schema and no annotations, so the description must define the full contract; it covers format acceptance, validation rules, failure remediation and follow-up tools well. The notable gap is what a successful call returns — an import id, a queued job, or booked entries — which an agent would need for the next step.

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 0% for all three required parameters, so the description must compensate, and it only explains file_base64 (raw bytes, base64). The filename (whether it must carry an extension, how it is used) and company_id are left entirely to inference.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource up front ("Import a BANK STATEMENT") and then differentiates handling by format: CAMT.053 XML books immediately, PDF/CSV/.xlsx queue, .zip splits, legacy .xls and UTF-16 CSV are refused. That is far more than a restatement of the name, though it never contrasts itself with adjacent siblings like upload_accounting_import or upload_document.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete conditional rules — CSV/.xlsx only proceed when opening + lines equal closing, otherwise nothing is imported, and a missing printed balance blocks the import until values arrive via assign_bank_statement_import_accounts. It also routes queued results to list_bank_statement_imports. It lacks explicit when-not-to-use guidance versus other upload tools.

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