Skip to main content
Glama

Parse camt.053 statement file

parse_camt053
Read-onlyIdempotent

Parse a camt.053 bank-statement XML file on disk into structured data. Optionally validate against an XSD before parsing.

Instructions

Parse a camt.053 bank-statement XML file on disk into structured data.

Use this to read a bank's account statement (the reply that confirms
settlement) into a header + entry list. Reads ``xml_file_path`` from the
local filesystem. For the payment-status reply (accepted/rejected per
transaction) use ``parse_pain002`` instead; to validate a camt.053
string you already hold, this is not it — this tool needs a file path.

Wraps :func:`pain001.parse_camt053_statement`. When ``xsd_file_path``
is provided, the document is first validated against that XSD; on a
schema or parse error the tool returns ``{"error": ...}`` rather than
raising.

Args:
    xml_file_path: Filesystem path to the camt.053 XML statement.
    xsd_file_path: Optional path to a camt.053 XSD for upfront
        validation.

Returns:
    A compact dict with the statement header and entry list, or an
    ``{"error": ...}`` payload on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xml_file_pathYesLocal filesystem path to the camt.053 bank-statement XML file to parse.
xsd_file_pathNoOptional local path to a camt.053 XSD; when given, the document is validated against it before parsing. Omit to skip schema validation.
Behavior5/5

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

Discloses reading from local filesystem, optional XSD validation, and error return style ({"error": ...}) instead of exceptions. Annotations confirm read-only, non-destructive, idempotent; description aligns with no contradictions.

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?

Well-structured: main purpose first, then usage guidance, then details. Every sentence adds value; no redundancy. Efficiently conveys all needed info.

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

Completeness5/5

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

Completes the picture: explains input (file path), optional validation, output format (header + entry list or error). No output schema needed given compact description.

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 100% and description adds context about local filesystem reading and error behavior, but parameter descriptions are already clear in schema. Adds moderate value beyond schema.

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 clearly states it parses a camt.053 bank-statement XML file into structured data, using specific verb 'Parse' and resource. It distinguishes from sibling tool parse_pain002 which handles payment-status replies.

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 when to use (for account statements) and when not (for payment-status replies, for in-memory strings). Names alternative tool parse_pain002 and notes this tool requires a file path.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/pain001-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server