Skip to main content
Glama

ISO 20022 Structured & Hybrid <PstlAdr> Registry Cure

iso20022_cbpr_cure
Read-onlyIdempotent

Resolves live statutory registries (GLEIF, UK Companies House, Norway Brreg) into schema-bounded ISO 20022 Structured/Hybrid and pain.001 XML with signed receipt.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lei": "506700GE1G29325QX363",
      "target_mode": "STRUCTURED"
    },
    "name": "iso20022_cbpr_cure"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiNo20-character LEI to resolve via GLEIF
xmlNoOptional raw ISO 20022 pain.001 XML to cure unstructured <AdrLine> blocks
uk_crnNoUK company registration number
no_orgnrNo9-digit Norwegian organization number
target_modeNoTarget ISO 20022 address output mode (default STRUCTURED)
allow_heuristic_fallbackNoAllow caller-supplied address fallback when live registry lookup fails

Output Schema

NameRequiredDescriptionDefault
validNo
target_modeNo
canonical_addressNo
cured_pain001_xmlNo
pstl_adr_hybrid_xmlNo
pstl_adr_structured_xmlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds that lookups hit live external registries and that output includes a signed receipt, but says nothing about failure behavior, rate limits, or what happens when a live lookup misses.

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?

A single front-loaded sentence with no filler, and the registry sources and output artifacts are packed in efficiently. It is dense with domain jargon, but nothing is wasted.

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, but the tool has six optional parameters and the description never states that some identifier must be supplied or how modes interact. For a resolver with that much input flexibility, the description leaves a meaningful gap.

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 six parameters are already documented in the schema; the description only echoes the registry concept. It does not clarify the important ambiguity of how the optional identifiers combine or what happens with zero identifiers supplied.

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?

Names a specific verb ("Resolves") and resource (live statutory registries GLEIF/UK Companies House/Norway Brreg) and states the output artifact (schema-bounded ISO 20022 Structured/Hybrid <PstlAdr> and pain.001 XML with signed receipt). This clearly separates it from a validator like iso20022_validate, though the term "cure" is jargon and is never defined.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no hint about which identifier (lei vs uk_crn vs no_orgnr vs raw xml) selects which registry path. The agent must infer usage entirely from the parameter names.

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.