Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

Parse camt.052/053/054 statements

bank-payments_camt053-parse
Read-onlyIdempotent

Parse an ISO 20022 bank-to-customer statement or report into normalised JSON with balance reconciliation checks. Price $0.03 USDC. POST /api/v1/bank-payments/camt053-parse. An unpaid call returns the x402 payment terms and does not run.

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": {
      "xml": "<xml>"
    },
    "name": "bank-payments_camt053-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesxml, string, length 20 to 10000000. Required.
includeRawNoincludeRaw, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
checksNochecks. Object.
sourcesNosources. Array.
statementsNostatements. Array.
limitationsNolimitations. Array.
messageTypeNomessageType. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a $0.03 USDC price, the concrete POST endpoint, and the fact that an unpaid call short-circuits and returns payment terms instead of executing. It stops short of stating rate limits, size limits, or what the reconciliation check does when balances fail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the verb and resource, then price/endpoint, then the payment-gate caveat. No redundant or filler wording; every clause carries information.

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?

An output schema exists, so return-value explanation is unnecessary, and the payment/auth behavior is disclosed. The remaining gap is format scope: the title names camt.052/053/054 while the description says only "statement or report", leaving an agent unsure whether non-camt.053 variants or pain messages are accepted.

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% and both parameters (xml, includeRaw) are documented in the schema itself, so the baseline of 3 applies. The description adds no meaning about the xml payload, accepted message versions, or what includeRaw returns 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?

"Parse an ISO 20022 bank-to-customer statement or report into normalised JSON with balance reconciliation checks" gives a specific verb (parse), a specific resource (ISO 20022 bank-to-customer statement/report), and the output shape. Siblings are all validators/builders (iban, nacha, sepa, uetr, modulus), so no agent could confuse this with them.

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

Usage Guidelines3/5

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

The description implies the use case (turning camt XML into JSON) but never states when to prefer it over alternatives, nor any prerequisites such as which camt versions or message types are accepted. The one conditional it does give — "An unpaid call returns the x402 payment terms and does not run" — is about payment flow rather than tool selection.

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