Skip to main content
Glama
Sign In
camt053-mcp

camt053-mcp

by sebastienrousseau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get input JSON Schema

get_input_schema
Read-onlyIdempotent

Get a complete JSON Schema for any supported ISO 20022 camt.05x message type, revealing all fields, types, and constraints to build valid records or drive a UI.

Instructions

Return the full JSON Schema for a message type's flat input record.

Use this to learn every field, its type, and its constraints before
assembling records, or to drive a form/UI. For just the required-field
names use ``get_required_fields``; to actually check records against this
schema use ``validate_records``.

Args:
    message_type: A supported ISO 20022 camt.05x message type.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message_type": "<message_type>"
    },
    "name": "get_input_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_typeYesA supported ISO 20022 camt.05x message type string. Must be exactly one of: 'camt.052.001.14', 'camt.053.001.14', 'camt.054.001.14' (see list_message_types).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / message_type / description
      Previous value: -"A supported ISO 20022 camt.05x message type string, e.g. 'camt.053.001.14'. Call list_message_types first to discover the exact accepted values."New value: +"A supported ISO 20022 camt.05x message type string. Must be exactly one of: 'camt.052.001.14', 'camt.053.001.14', 'camt.054.001.14' (see list_message_types)."
    • addedInput schema / properties / message_type / enum
      Added value: +[
+  "camt.052.001.14",
+  "camt.053.001.14",
+  "camt.054.001.14"
+]
  2. Changed1 schema field changedv0.0.12
    • addedInput schema / properties / message_type / description
      Added value: +"A supported ISO 20022 camt.05x message type string, e.g. 'camt.053.001.14'. Call list_message_types first to discover the exact accepted values."
  3. First observedv0.0.11

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds context about returning a 'full JSON Schema for a flat input record', but does not disclose any additional behavioral traits beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the purpose, followed by clear usage guidance and parameter description. No superfluous content.

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 single parameter, no output schema, and low complexity, the description fully covers what the tool does, when to use it, and the parameter's meaning, leaving no gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with the schema already describing the 'message_type' parameter. The description adds value by referencing 'list_message_types' for valid values and clarifying its use in the context of ISO 20022 camt.05x messages.

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?

The description clearly states the verb 'Return' and the resource 'full JSON Schema for a message type's flat input record'. It distinguishes from siblings by mentioning 'get_required_fields' and 'validate_records'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use ('to learn every field... or to drive a form/UI') and when not to ('For just the required-field names... to actually check records...'), naming alternative tools directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools