acmt001-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 |
|---|---|
| list_message_typesA | List every supported ISO 20022 acmt message type and its human name. |
| get_required_fieldsA | List only the required input field names for an acmt message type. |
| get_input_schemaA | Return the full JSON Schema for a message type's flat input record. |
| validate_recordsA | Validate flat account records against a message type's input JSON Schema. |
| validate_identifierA | Validate a single financial identifier (IBAN, BIC, or LEI). |
| generate_messageA | Generate a validated ISO 20022 acmt XML message from in-memory records. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a unique, clearly defined purpose: listing message types, retrieving schema details, validating records or identifiers, and generating XML. No two tools overlap in functionality.
All tool names follow the same verb_noun pattern in lowercase with underscores (e.g., list_message_types, validate_records), providing a predictable and uniform interface.
With 6 tools, the server covers the essential workflow—discovery, schema inspection, validation, and generation—without being bloated or too sparse for its stated purpose.
The tools provide a complete lifecycle for generating validated acmt XML messages: discover supported types, examine field requirements, validate inputs at both record and identifier level, and produce the final XML.