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

ISO 20022 Payment Evidence & Investigation MCP

lookup_code

Look up an ISO 20022 status reason, transaction status or charge bearer code. Use this instead of guessing.

Instructions

Look up an ISO 20022 status reason, transaction status or charge bearer code. Use this instead of guessing.

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": {
      "code": "<code>"
    },
    "name": "lookup_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

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": "lookup_codeOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses very little. Read-only nature is only implied by "look up"; nothing is said about what an unknown or ambiguous code produces, whether the code sets are disambiguated automatically, or what the response contains. The one useful signal is the enumeration of supported code families.

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 short sentences with zero filler, and the resource scope is front-loaded before the usage advice. Nothing could be cut without losing information.

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?

For a one-parameter lookup tool this is nearly adequate, but with no annotations and no output schema the description should say what a lookup actually returns (a definition, a name, an error on unknown code). As written, an agent knows when to call it but not what it will get back.

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 0% for the single `code` parameter, so the description must compensate. It helps by naming the three code families the value may belong to, but it never states the expected format or how to disambiguate between overlapping code namespaces, leaving real ambiguity about what string to pass.

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?

"Look up an ISO 20022 status reason, transaction status or charge bearer code" gives a specific verb plus a precisely scoped resource, and the three named code families make it clearly distinct from parse_message, validate_message and explain_message. It stops short of 5 only because the distinction from siblings is achieved by implication rather than explicit contrast.

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?

"Use this instead of guessing" supplies a genuine usage trigger: reach for this tool when a code's meaning is unknown rather than inferring it. It does not state any when-not condition, prerequisites, or which sibling to use when the question is about a whole message rather than a bare code, so guidance stays at the implied level.

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