Skip to main content
Glama
sebastienrousseau

camt-exceptions

by sebastienrousseau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_message_typesA

List supported ISO 20022 Exceptions & Investigations message types.

Purpose: Returns the catalog of supported E&I message identifiers (e.g. camt.056.001.12 Payment Cancellation Request, camt.029.001.14 Resolution of Investigation) and their human-readable definitions.

When to use:

  • When discovering valid message_type parameters before generating or validating messages.

  • When verifying schema version support for payment recall or resolution workflows.

When NOT to use:

  • Do NOT use for payment initiation (pain) or statement (camt.053) messages.

Behavioral transparency: Static catalogue retrieval; pure, deterministic, and side-effect-free.

get_required_fieldsA

Get required schema fields for an ISO 20022 E&I message type.

Purpose: Returns the list of mandatory top-level data fields required to construct a valid message record (e.g. assignment identification, instruct team agent, and transaction arrays).

When to use:

  • When preparing input payloads before calling generate_message.

  • When validating payload completeness prior to XML serialization.

When NOT to use:

  • Do NOT use with unsupported message types; discover supported types via list_message_types.

Behavioral transparency: Deterministic field dictionary lookup; pure, read-only, and idempotent.

generate_messageA

Generate a schema-validated ISO 20022 E&I XML message from a record.

Purpose: Renders a complete, XSD-compliant ISO 20022 XML document (e.g. camt.056 payment cancellation or camt.029 investigation resolution) from structured field dictionaries, validating the result against the bundled official schema before returning.

When to use:

  • When raising payment cancellation, recall, or investigation response messages for interbank transmission.

  • When requiring guaranteed XSD-valid XML output for downstream payment processing.

When NOT to use:

  • Do NOT use to validate pre-existing XML files without generating; use validate_xml instead.

  • Do NOT pass incomplete records; check get_required_fields first.

Behavioral transparency: Pure template rendering and in-memory schema validation; side-effect-free and idempotent.

validate_xmlA

Validate raw ISO 20022 E&I XML against bundled XSD schemas.

Purpose: Validates an XML string against the official bundled XSD schema for the specified E&I message type, returning validation status and detailed schema violation diagnostics.

When to use:

  • When inspecting received or pre-generated ISO 20022 E&I XML before ingesting or routing.

  • When diagnosing schema structural, datatype, or constraint errors in message payloads.

When NOT to use:

  • Do NOT use for payment initiation (pain) or statement (camt.053) documents.

  • Do NOT pass unparseable binary content; requires valid XML text.

Behavioral transparency: Pure, in-memory schema validation using local bundled XSDs; zero network access or side effects.

Prompts

Interactive templates invoked by user choice

NameDescription
build_investigation_messageGuide the caller through building a validated E&I ``camt`` message.

Resources

Contextual data attached and managed by the client

NameDescription
message_types_resourceThe supported ISO 20022 Exceptions & Investigations message types and their names, as JSON.
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct stage of the E&I message workflow: catalogue discovery (list_message_types), schema field lookup (get_required_fields), XML rendering (generate_message), and XML validation (validate_xml). Descriptions explicitly cross-reference alternatives (e.g. 'use validate_xml instead'), leaving no ambiguity.

Naming Consistency5/5

All four names follow a consistent snake_case verb_noun pattern: list_message_types, get_required_fields, generate_message, validate_xml. Verb-first, predictable, and readable throughout.

Tool Count4/5

Four tools form a tight, well-scoped workflow for a focused domain (ISO 20022 E&I message generation and validation). Slightly lean, but each tool clearly earns its place with no redundancy.

Completeness4/5

The surface covers the full lifecycle: discover valid message types, learn required fields, generate XSD-valid XML, and validate existing XML. Minor gaps exist (e.g. no batch validation or per-type example payloads), but core workflows are fully supported.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources