camt-exceptions
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 |
|---|---|
| list_message_typesA | List the supported ISO 20022 Exceptions & Investigations message types (e.g. camt.056 payment cancellation request) and their names. |
| get_required_fieldsA | Return the required top-level fields for an E&I message type. |
| generate_messageA | Generate a validated ISO 20022 E&I XML message from a record. For camt.056, the record cancels/recalls a previously sent payment (assignment ids + agent BICs + a list of 'transactions' with the original payment references and a cancellation reason code). Output is validated against the bundled XSD before it is returned. |
| validate_xmlA | Validate raw ISO 20022 XML against an E&I message type's bundled XSD; returns is_valid plus any schema errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_investigation_message | Guide the caller through building a validated E&I ``camt`` message. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| message_types_resource | The supported ISO 20022 Exceptions & Investigations message types and their names, as JSON. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing message types, retrieving required fields, generating a message, and validating XML. No overlapping functionality.
All tool names follow a consistent verb_noun pattern with underscores (e.g., list_message_types, generate_message), making them predictable and easy to understand.
With 4 tools, the set is well-scoped for the domain of ISO 20022 Exceptions & Investigations message generation and validation. Each tool serves a necessary function without redundancy.
The tools cover the core workflow of listing types, getting schema details, generating messages, and validating them. A minor gap exists in that generate_message specifically mentions camt.056, but the description implies support for other types as well. Lacks tools for parsing or transforming existing messages, but the set is reasonably complete for its intended purpose.