Skip to main content
Glama

normalize_pain001

Read-onlyIdempotent

Convert parsed pain.001 payment instructions into canonical expected records for reconciliation. Maps diverse payment fields to uniform id, amount, and reference fields.

Instructions

Convert parsed pain.001 payment instructions into canonical expected records.

Purpose: Adapts parsed ISO 20022 pain.001 credit transfer documents or transaction lists into canonical expected records ready for the reconcile engine.

When to use:

  • When converting parsed pain.001 files into canonical expected records for reconcile.

  • When mapping diverse payment field structures into uniform id, amount, and reference fields.

When NOT to use:

  • Accepts parsed pain.001 payment orders only, not bank statement entries (camt.053); use normalize_camt053 for statements.

  • Expects a parsed dictionary or list rather than raw XML text.

Behavioral transparency: Pure, deterministic, read-only data normalization.

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": {
      "document": "<document>"
    },
    "name": "normalize_pain001"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYesParsed pain.001 document or transaction list.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Pure, deterministic, read-only data normalization' largely restates structured data. The genuinely additive parts are the input-format constraint (no raw XML) and the note that output feeds the reconcile engine; nothing is said about error behavior or partial/invalid input handling.

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?

Labelled sections with the purpose and scope constraint front-loaded, followed by compact use/exclusion lists. Headers are short and every line adds routing or behavioral information rather than filler.

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?

An output schema exists, so return values need not be explained, and the single parameter plus annotations are well covered. The only minor gap is whether batches of multiple documents are handled or what happens with malformed parsed input.

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

Parameters4/5

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

Schema coverage is 100% and the single 'document' parameter is already described, so the baseline is a 3. The description earns an extra point by clarifying that the value must be a parsed dictionary or transaction list rather than raw XML text, and by naming what gets mapped (id, amount, reference fields).

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 ('Convert parsed pain.001 payment instructions into canonical expected records') and explicitly names the sibling it is not for (normalize_camt053). An agent can distinguish it from the statement normalizer without opening either schema.

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?

Provides explicit 'When to use' and 'When NOT to use' sections, names the alternative (normalize_camt053 for camt.053 statements), and adds an input-format precondition (parsed dictionary/list, not raw XML). Routing decisions are fully determined by the text.

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