Skip to main content
Glama
ISO 20022 Payment Evidence & Investigation MCP

ISO 20022 Payment Evidence & Investigation MCP

validate_message

Validate a pacs.008/pacs.002 message against business rules (IBAN checksum, BIC format, amounts, required parties, counts, free-text limits, prompt-injection patterns). Returns issues with likely reject codes.

Instructions

Validate a pacs.008/pacs.002 message against business rules (IBAN checksum, BIC format, amounts, required parties, counts, free-text limits, prompt-injection patterns). Returns issues with likely reject codes.

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": {
      "xml": "<xml>"
    },
    "name": "validate_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "validate_messageOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the checks performed and that the response is a list of issues with likely reject codes, but says nothing about whether validation short-circuits on the first error, how malformed or non-pacs XML is handled, or whether the operation is purely read-only.

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 sentences, front-loaded with the action and scope, with the rule list and return behavior following. The parenthetical enumeration is dense but each item conveys a distinct check, so no wording is wasted.

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?

For a single-parameter tool with no output schema, the description covers purpose, rule coverage, and a summary of the return value (issues plus likely reject codes). The remaining gap is the absence of any detail on issue object shape or failure modes, which is minor given the tool's simplicity.

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 0% and the single 'xml' parameter is only titled 'Xml', so the description must compensate. It does clarify that the payload should be a pacs.008 or pacs.002 message, which meaningfully narrows what belongs in that string, but adds no format, encoding, or size guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (Validate) and resource (pacs.008/pacs.002 message) and enumerates the rule families checked, so the agent knows exactly what the tool does. It does not explicitly contrast itself with siblings like parse_message or explain_message, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the verb 'Validate' and the listed business rules, which suggests a pre-submission check, but the description never states when to choose this over parse_message or explain_message, nor any prerequisites. No explicit when-not guidance is given.

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