Skip to main content
Glama

ISO 20022 validator

submit_iso20022_validator
Idempotent

Validate an ISO 20022 payment message for its required blocks and fields, and total the amounts. Before sending a payment message, to catch missing elements. Do not choose this when full XSD schema validation is required. Example requests: Validate this ISO 20022 payment message. | Is my pain.001 message complete? | Check this payment XML for missing fields.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_iso20022_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description adds the useful note that amounts are totalled. However, it never explains what the non-read-only behavior entails — the tool runs as a priced job needing quote authorization and price acceptance, which is a significant trait left to the schema. With annotations carrying part of the load, this lands at a 3.

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

Conciseness3/5

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

The purpose is front-loaded, which is good, but the body is written as clipped fragments ('Before sending a payment message, to catch missing elements.') rather than full sentences. The example-request list is useful for intent matching but adds length that isn't strictly needed once the scope is stated.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the validation scope is clear. What is missing relative to this tool's complexity is the job/pricing model — that submission is authorized against a quote and that a price can be refused — which the description never surfaces.

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 75% and the nested message, quote_id, authorized_by and accepted_price fields are all documented in the schema itself. The description contributes no syntax, format, or size guidance beyond what the schema states, so the 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?

The first clause names a specific verb and resource ('Validate an ISO 20022 payment message') and narrows scope to 'required blocks and fields, and total the amounts'. This distinguishes it from neighbours such as submit_iban_bic_validator or submit_sepa_payment_file_builder without needing their schemas.

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

Usage Guidelines4/5

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

'Before sending a payment message, to catch missing elements' gives a clear trigger, and 'Do not choose this when full XSD schema validation is required' provides an explicit exclusion. It stops short of a 5 because the excluded alternative (e.g. submit_json_schema_validation) is never named, so the agent must infer the routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources