pain001-mcp

Validate XML string against XSD

validate_xml_against_schema

Read-onlyIdempotent

Check a pain.001 or pain.008 XML string against its official XSD without filesystem access. Returns whether it is valid and error details when invalid.

Instructions

Validate a raw pain.001 / pain.008 XML string against its official XSD.

Use this to check XML you already have as a string (e.g. received from
another system) without touching the filesystem. To validate records
*before* they become XML, use ``validate_records``; to parse a statement
or status-report file, use ``parse_camt053`` / ``parse_pain002``.

Wraps :func:`pain001.xml.validate_via_xsd.validate_xml_string_via_xsd`.

Args:
    xml_content: The XML document as a string.
    message_type: A supported ISO 20022 pain message type.

Returns:
    ``{"valid": bool, "message_type": str, "error": str?}`` -
    ``error`` is present only when ``valid`` is ``False``.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`xml_content`	Yes	The full pain.001 / pain.008 XML document as a string, validated against the message type's official XSD.
`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: -"The ISO 20022 pain message type whose XSD to validate against, e.g. 'pain.001.001.09' — 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' (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"
+]

Changed2 schema fields changedv0.0.56Jul 10, 2026

addedInput schema / properties / message_type / description

Added value: +"The ISO 20022 pain message type whose XSD to validate against, e.g. 'pain.001.001.09' — see list_message_types."

addedInput schema / properties / xml_content / description

Added value: +"The full pain.001 / pain.008 XML document as a string, validated against the message type's official XSD."

First observedJul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, local-only. The description adds the filesystem-independence constraint and describes the return shape including the conditional 'error' key present only when invalid, which is genuine behavioral context beyond the annotations. Missing details like whether it short-circuits on first error or reports all errors.

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

Conciseness4/5

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

Front-loaded purpose sentence followed by routing guidance, then Args/Returns. Efficient overall, though the Args section is redundant with the 100%-covered schema and the cross-reference to pain001.xml.validate_via_xsd.validate_xml_string_via_xsd is implementation leakage that adds little for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by documenting the return dict with its conditional error field. Combined with full parameter coverage and explicit sibling routing, an agent has enough to invoke correctly. Could note error detail granularity for higher completeness.

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 enum values are fully documented in the schema, including the alias behavior for bare 'pain.001'/'pain.008'. The description's Args block merely restates what the schema already provides, so it adds no meaning beyond the structured data. Baseline 3 applies.

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+resource+scope ('Validate a raw pain.001 / pain.008 XML string against its official XSD') and explicitly distinguishes itself from siblings by naming validate_records, parse_camt053, and parse_pain002.

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?

Explicit when-to-use ('check XML you already have as a string ... without touching the filesystem') and named alternatives for adjacent use cases (validate_records for pre-XML records, parse_camt053/parse_pain002 for statement/status files). Routing is unambiguous.

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

Validate XML string against XSD

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools