pain001-mcp

Get input JSON Schema

get_input_schema

Read-onlyIdempotent

Retrieve the complete JSON Schema for a supported ISO 20022 pain message type's flat input record, so you can inspect every field, type, and constraint before assembling or validating records.

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 pain message type.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`message_type`	Yes	A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.001.001.13', 'pain.008.001.02', 'pain.008.001.08', 'pain.001', 'pain.008' (see list_message_types). The bare family names 'pain.001' and 'pain.008' are accepted as aliases for 'pain.001.001.09' and 'pain.008.001.02'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.0.67Sep 12, 2026

changedInput schema / properties / message_type / description

Previous value: -"A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.001.001.13', 'pain.008.001.02', 'pain.001', 'pain.008' (see list_message_types). The bare family names 'pain.001' and 'pain.008' are accepted as aliases for 'pain.001.001.09' and 'pain.008.001.02'."New value: +"A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.001.001.13', 'pain.008.001.02', 'pain.008.001.08', 'pain.001', 'pain.008' (see list_message_types). The bare family names 'pain.001' and 'pain.008' are accepted as aliases for 'pain.001.001.09' and 'pain.008.001.02'."

changedInput schema / properties / message_type / enum

Previous value: -[
-  "pain.001.001.03",
-  "pain.001.001.04",
-  "pain.001.001.05",
-  "pain.001.001.06",
-  "pain.001.001.07",
-  "pain.001.001.08",
-  "pain.001.001.09",
-  "pain.001.001.10",
-  "pain.001.001.11",
-  "pain.001.001.12",
-  "pain.001.001.13",
-  "pain.008.001.02",
-  "pain.001",
-  "pain.008"
-]New value: +[
+  "pain.001.001.03",
+  "pain.001.001.04",
+  "pain.001.001.05",
+  "pain.001.001.06",
+  "pain.001.001.07",
+  "pain.001.001.08",
+  "pain.001.001.09",
+  "pain.001.001.10",
+  "pain.001.001.11",
+  "pain.001.001.12",
+  "pain.001.001.13",
+  "pain.008.001.02",
+  "pain.008.001.08",
+  "pain.001",
+  "pain.008"
+]

Changed2 schema fields changedJul 29, 2026

changedInput schema / properties / message_type / description

Previous value: -"A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.008.001.02', 'pain.001', 'pain.008' (see list_message_types). The bare family names 'pain.001' and 'pain.008' are accepted as aliases for 'pain.001.001.09' and 'pain.008.001.02'."New value: +"A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.001.001.13', 'pain.008.001.02', 'pain.001', 'pain.008' (see list_message_types). The bare family names 'pain.001' and 'pain.008' are accepted as aliases for 'pain.001.001.09' and 'pain.008.001.02'."

changedInput schema / properties / message_type / enum

Previous value: -[
-  "pain.001.001.03",
-  "pain.001.001.04",
-  "pain.001.001.05",
-  "pain.001.001.06",
-  "pain.001.001.07",
-  "pain.001.001.08",
-  "pain.001.001.09",
-  "pain.001.001.10",
-  "pain.001.001.11",
-  "pain.001.001.12",
-  "pain.008.001.02",
-  "pain.001",
-  "pain.008"
-]New value: +[
+  "pain.001.001.03",
+  "pain.001.001.04",
+  "pain.001.001.05",
+  "pain.001.001.06",
+  "pain.001.001.07",
+  "pain.001.001.08",
+  "pain.001.001.09",
+  "pain.001.001.10",
+  "pain.001.001.11",
+  "pain.001.001.12",
+  "pain.001.001.13",
+  "pain.008.001.02",
+  "pain.001",
+  "pain.008"
+]

Addedv0.0.60Jul 18, 2026
RemovedJul 18, 2026

Changed2 schema fields changedJul 17, 2026

changedInput schema / properties / message_type / description

Previous value: -"A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.008.001.02' (see list_message_types)."New value: +"A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.008.001.02', 'pain.001', 'pain.008' (see list_message_types). The bare family names 'pain.001' and 'pain.008' are accepted as aliases for 'pain.001.001.09' and 'pain.008.001.02'."

changedInput schema / properties / message_type / enum

Previous value: -[
-  "pain.001.001.03",
-  "pain.001.001.04",
-  "pain.001.001.05",
-  "pain.001.001.06",
-  "pain.001.001.07",
-  "pain.001.001.08",
-  "pain.001.001.09",
-  "pain.001.001.10",
-  "pain.001.001.11",
-  "pain.001.001.12",
-  "pain.008.001.02"
-]New value: +[
+  "pain.001.001.03",
+  "pain.001.001.04",
+  "pain.001.001.05",
+  "pain.001.001.06",
+  "pain.001.001.07",
+  "pain.001.001.08",
+  "pain.001.001.09",
+  "pain.001.001.10",
+  "pain.001.001.11",
+  "pain.001.001.12",
+  "pain.008.001.02",
+  "pain.001",
+  "pain.008"
+]

Changed2 schema fields changedv0.0.57Jul 10, 2026

changedInput schema / properties / message_type / description

Previous value: -"A supported ISO 20022 pain message type, e.g. 'pain.001.001.09' — see list_message_types for the exact accepted strings."New value: +"A supported ISO 20022 pain message type. Must be exactly one of: 'pain.001.001.03', 'pain.001.001.04', 'pain.001.001.05', 'pain.001.001.06', 'pain.001.001.07', 'pain.001.001.08', 'pain.001.001.09', 'pain.001.001.10', 'pain.001.001.11', 'pain.001.001.12', 'pain.008.001.02' (see list_message_types)."

addedInput schema / properties / message_type / enum

Added value: +[
+  "pain.001.001.03",
+  "pain.001.001.04",
+  "pain.001.001.05",
+  "pain.001.001.06",
+  "pain.001.001.07",
+  "pain.001.001.08",
+  "pain.001.001.09",
+  "pain.001.001.10",
+  "pain.001.001.11",
+  "pain.001.001.12",
+  "pain.008.001.02"
+]

Changed1 schema field changedv0.0.56Jul 10, 2026

addedInput schema / properties / message_type / description

Added value: +"A supported ISO 20022 pain message type, e.g. 'pain.001.001.09' — see list_message_types for the exact accepted strings."

First observedJul 9, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety profile is covered. The description adds that the schema represents a 'flat input record' and that field constraints are included, but doesn't describe output format (JSON Schema structure) or whether there are size limits. With annotations carrying the safety profile, a 3 is appropriate.

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?

Three sentences with zero waste: first states purpose, second gives usage context, third names alternatives with their specific function. Front-loaded with the core action and appropriately concise.

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?

Complete for a read-only schema retrieval tool with no output schema, one fully documented parameter, and annotations covering safety. The description provides enough for an agent to understand when and how to call it correctly, including routing to alternatives.

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

Parameters3/5

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

Schema coverage is 100% and the parameter is fully documented in the schema with enum values and alias explanation. The description only repeats that message_type is 'a supported ISO 20022 pain message type', adding no additional syntax or format details beyond the schema. Baseline 3 is correct when schema does the heavy lifting.

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?

States a specific verb and resource ('Return the full JSON Schema for a message type's flat input record') and names a clear scope. It distinguishes itself from siblings get_required_fields and validate_records by describing exactly what each alternative returns or does.

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 gives the purpose ('learn every field, its type, and its constraints before assembling records, or to drive a form/UI') and routes to sibling tools with distinct conditions: use get_required_fields for only required names, and validate_records to check records against this schema. No inference needed.

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

Get input JSON Schema

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools