iso20022-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the ISO 20022 catalogue by use-case, message type or keyword (e.g. 'reconciliation', 'make a payment', 'pacs.008') and get the matching message types, their family, and which package provides them. |
| list_familiesA | List every ISO 20022 family the gateway routes to (pain, pacs, camt, acmt): its capabilities, backing package, and whether that package is installed in this environment. |
| list_serversA | List the whole ISO 20022 suite the gateway knows: the message families (pain/pacs/camt/acmt), the Exceptions & Investigations messages (camt.056/camt.029), and the specialized servers (reconciliation, agent-payment bridge) with what each does. |
| describeA | Describe a message type: its required fields and input JSON Schema, resolved from the family's backing server. |
| validateA | Validate records for a message type against its JSON Schema, via the family's backing server. |
| generateA | Generate a validated ISO 20022 XML message from records; the XML document is returned in the 'xml' key. Supported for initiation and interbank families (pain, pacs, acmt); statement families (camt) are inbound-only and return an explanatory error. On failure the 'error' value lists every missing or invalid field at once — fix them all and retry once. |
| parseA | Parse an inbound ISO 20022 XML message into structured data. Parse coverage is per-family: pacs (e.g. pacs.008) and camt (e.g. camt.053) only. The initiation families pain and acmt are outbound-only — they have NO parser here, so do not attempt a generate→parse round-trip for pain.001 or acmt.001; use 'validate' or the backing server's XSD validation instead. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| route_iso20022_task | Guided prompt teaching the model how to route a task across the gateway. The MCP client sends this to the model to establish the recommended meta-tool order so it uses the gateway correctly instead of guessing a message type. Args: goal: The payments task in plain language. Returns: A prompt string instructing the model how to proceed. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| families_resource | Expose the routed ISO 20022 families as a JSON resource. Returns the same family catalogue as the ``list_families`` tool (:func:`registry.family_summary`) -- each family's capabilities, backing package, and whether that package is installed here -- serialised as JSON, so an agent can load the suite map as reference context without a tool call. Mirrors the ``list_families`` tool, which takes no arguments and cannot fail, so no error envelope is needed. |
| servers_resource | Expose the full ISO 20022 suite map as a JSON resource. Returns the same payload as the ``list_servers`` tool (:func:`registry.list_all_servers`) -- message families, the Exceptions & Investigations messages, and the specialised servers -- serialised as JSON. Mirrors the ``list_servers`` tool, which takes no arguments and cannot fail, so no error envelope is needed. |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but list_families and list_servers overlap in listing families, which could cause confusion. Search, describe, validate, generate, and parse are clearly differentiated.
All tool names follow a verb or verb_noun pattern using snake_case, e.g., list_families, describe, generate. No mixed conventions or inconsistent casing.
With 7 tools covering discovery, schema retrieval, validation, generation, and parsing, the count is well-scoped for the domain of ISO 20022 message handling.
The tool set covers the core lifecycle: discovery, schema, validation, generation, and parsing. However, generation and parsing are asymmetric across families (e.g., no parse for pain/acmt), leaving minor gaps.