Skip to main content
Glama

Convert MT103 to pacs.008 records

convert_mt103
Read-onlyIdempotent

Convert a legacy SWIFT MT103 message into a flat pacs.008 record for ISO 20022 migration. Parses MT103 text and returns a single record ready for validation and message generation.

Instructions

Convert a legacy SWIFT MT103 into pacs.008-ready flat records.

This is the SWIFT MT-to-MX migration path (correspondent-banking MT103
coexistence with ISO 20022 ends November 2025): parse an MT103 text
payload and get back the flat pacs.008 record(s) that can be fed straight
into ``validate_records`` / ``generate_message``. An MT103 carries exactly
one transfer, so the ``records`` list always holds a single record. No
file is read or written.

Returns ``{"message_type": "pacs.008.001.08", "records": [{...}]}`` with
the parsed flat record, or an ``{"error": ...}`` payload if the MT103 is
missing a mandatory field (``:20:``, ``:32A:``, beneficiary) or malformed.

Args:
    mt103_text: The MT103 payload as a string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mt103_textYesA legacy SWIFT MT103 (single customer credit transfer) payload as text. A raw '{4:...-}' block-4 envelope, trailing whitespace and CRLF/LF differences are tolerated.
Behavior5/5

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

Discloses that the tool parses MT103 text, always returns a single record, no file I/O, and error cases when mandatory fields are missing. Annotations already indicated readOnly and idempotent, but the description adds specifics about return format and error handling.

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?

Description is front-loaded with purpose, followed by context and details. Slightly long due to background info on coexistence deadline, but every sentence is relevant. Could be trimmed slightly but still efficient.

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?

Given the complexity of a conversion tool with no output schema, the description fully covers return format, error scenarios, and integration with sibling tools. No gaps are identified.

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?

Single parameter mt103_text is fully described in the schema (100% coverage). The description repeats the parameter name and type ('The MT103 payload as a string') but adds no new details beyond the schema's already thorough description.

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?

Clearly states it converts MT103 to pacs.008 records, specifying verb and resource. Distinguishes from siblings like validate_records and generate_message by mentioning these as downstream tools. No ambiguity.

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?

Provides explicit context: SWIFT MT-to-MX migration path with a deadline (Nov 2025), and states the output feeds into validate_records/generate_message. Does not explicitly state when not to use or name alternatives, but the usage scenario is clear.

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/pacs008-mcp'

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