Skip to main content
Glama

parse_pain002_status_xml

Read-onlyIdempotent

Parses ISO 20022 pain.002 payment status XML to identify rejection codes and return plain-English remediation steps.

Instructions

Parse ISO 20022 pain.002 XML bank payment rejection reports (AC04, AM04, BE04, MD01) into plain-English remediation steps via Apify Cloud.

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_content": "<xml_content>"
    },
    "name": "parse_pain002_status_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
xml_contentYesRaw ISO 20022 pain.002.001.03 or pain.002.001.10 bank status report XML.
include_inline_csvNoWhen true, include a UTF-8 CSV summary of status records.
only_rejected_or_exceptionsNoWhen true, return only RJCT/PDNG transactions and omit ACCP items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds useful context that processing happens via Apify Cloud (an external service dependency) and that results are plain-English remediation steps, but says nothing about failure modes for unsupported XML, rate limits, or unsupported pain.002 versions.

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?

A single front-loaded sentence stating verb, resource, supported codes, output form, and backend. No filler or redundancy.

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?

With no output schema, the description usefully states what is returned (plain-English remediation steps) and the supported pain.002 versions appear in the schema. Minor gaps remain around error handling for malformed or unsupported XML, but overall it is complete enough to call correctly.

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 description coverage is 100%, so all three parameters are already documented with types, defaults, and meaning. The description adds no parameter-level detail beyond what the schema provides; baseline 3 applies.

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 names a specific verb (Parse) and resource (ISO 20022 pain.002 XML bank payment rejection reports), specifies the error codes handled (AC04, AM04, BE04, MD01), and states the output (plain-English remediation steps). This clearly separates it from the sibling generator/validator tools, though it doesn't explicitly name an alternative.

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 narrow resource scope (pain.002 rejection reports), but the description gives no explicit when-to-use, when-not-to-use, or alternative routing guidance. An agent must infer that this is the tool for pain.002 and not for other bank formats.

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