Skip to main content
Glama
Sign In
contabridge-mcp

contabridge-mcp

by ArceeDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Convert bank statement to bank-feed CSV

bank_statement_csv
Read-onlyIdempotent

Convert Norma 43 bank statements into CSV files formatted for Xero or QuickBooks Online import, with signed amounts and configurable date style.

Instructions

Turn a Norma 43 (Cuaderno 43) statement into a bank statement CSV that Xero or QuickBooks Online import.

target: xero (precoded statement: *Date, *Amount, Payee, Description, Reference) or quickbooks (3 columns: Date, Description, Amount). Amounts are signed (abono +, cargo -). date_style: mdy | dmy | iso (default mdy for QuickBooks, dmy for Xero). account: last digits of one bank account when the file holds several.

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": {
      "target": "<target>"
    },
    "name": "bank_statement_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
accountNo
contentNo
date_styleNo
content_base64No

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond them: the exact Xero precoded column set, the three-column QuickBooks layout, the sign convention (abono +, cargo -), and the per-target default date style — all things an agent could not infer from annotations.

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 compact and front-loaded, with the purpose in sentence one and parameter facts in a tight list. It is telegraphic to the point of terseness (fragments like 'target: xero (...) or quickbooks (...)'), which is efficient but occasionally reads like notes rather than prose.

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?

Because an output schema exists, return values need not be described, and the target/date_style semantics are well covered. The notable gap is the input payload: with both 'content' and 'content_base64' present and undocumented, an agent cannot tell which to populate, whether base64 encoding is required, or how conflicts are resolved — a meaningful omission for a five-parameter conversion tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema declares no enums, so the description does the heavy lifting: it effectively enumerates target (xero | quickbooks), date_style (mdy | dmy | iso) including per-target defaults, and explains account as 'last digits of one bank account'. The content and content_base64 parameters are never mentioned, leaving the file-supply mechanism unexplained.

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?

The description names a specific input format (Norma 43 / Cuaderno 43) and a specific output artifact (bank statement CSV for Xero or QuickBooks Online import) with a clear verb ('turn ... into'). That distinguishes it from siblings that produce journals (bank_to_journal, pdf_bank_to_journal) rather than import-ready CSVs.

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?

It makes the usage context explicit: pick 'target' xero or quickbooks, and use 'account' when the file holds several accounts. It gives no explicit exclusion or named alternative (e.g., when to prefer bank_to_journal instead), so it stops short of full routing guidance.

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