Skip to main content
Glama

AINumbers Fintech Intelligence Suite

ISO 20022-to-EVM Calldata Mapper

map_iso20022_to_evm_calldata
Read-onlyIdempotent

ISO 20022-to-EVM Calldata Mapper: OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node. By default (compute:"auto") inputs are computed server-side on Cloudflare Workers for gpu:false nodes with a registered kernel; compute:"browser" forces client-side execution and returns a browser delegation URL instead. gpu:true nodes always delegate to the browser. Inputs are processed transiently to compute the response and are not stored, logged, or retained. Use synthetic or anonymised inputs only. Exports an AP2 artifact with execution_hash for chain provenance. Output feeds: art-291-screen-onledger-transfer-batch. Open at: https://ainumbers.co/chaingraph/art-288-map-iso20022-to-evm-calldata.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Deterministic bind of an ISO 20022 pacs.008 (customer credit transfer) or pacs.009 (FI credit transfer) payment message to EVM contract-call arguments, plus an OCG receipt of the mapping: resolved call, field bindings, unmapped required fields, and ABI type coercions. Outputs: abi_type_coercions, draft_pinned, field_bindings, iso_message_type, mapping_ok, mapping_profile, mapping_profile_version, resolved_call, unmapped_required_fields, warnings. Output schema: call describe_tool("map_iso20022_to_evm_calldata").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "map_iso20022_to_evm_calldata"
  }
}

Input Schema

NameRequiredDescriptionDefault
computeNoCompute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always return browser delegation URL. gpu:true nodes always delegate.
parent_hashesNoexecution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
parent_tool_idsNotool_id values matching parent_hashes, in the same order.
policy_parametersNoInput parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "server". Required: contract_abi_fragment, iso_fields, iso_message_type, mapping_profile. Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changed
    • changedInput schema / properties / policy_parameters / description
      Previous value: -"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". See the tool's manifest for field names."New value: +"Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is \"auto\" or \"server\". Required: contract_abi_fragment, iso_fields, iso_message_type, mapping_profile. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "contract_abi_fragment": {},
      +  "iso_fields": {},
      +  "iso_message_type": {},
      +  "mapping_profile": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "abi_type_coercions": {
      -      "items": {
      -        "properties": {
      -          "abi_input": {
      -            "type": "string"
      -          },
      -          "coercion": {
      -            "type": "string"
      -          },
      -          "iso_field": {
      -            "type": "string"
      -          },
      -          "type": {
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "draft_pinned": {
      -      "type": "boolean"
      -    },
      -    "field_bindings": {
      -      "items": {
      -        "properties": {
      -          "abi_input": {
      -            "type": "string"
      -          },
      -          "iso_field": {
      -            "type": "string"
      -          },
      -          "resolved": {
      -            "type": "boolean"
      -          },
      -          "type": {
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "iso_message_type": {
      -      "type": "string"
      -    },
      -    "mapping_ok": {
      -      "type": "boolean"
      -    },
      -    "mapping_profile": {
      -      "type": "string"
      -    },
      -    "mapping_profile_version": {
      -      "type": "string"
      -    },
      -    "resolved_call": {
      -      "properties": {
      -        "args": {
      -          "items": {
      -            "type": "string"
      -          },
      -          "type": "array"
      -        },
      -        "function": {
      -          "type": "string"
      -        }
      -      },
      -      "type": "object"
      -    },
      -    "unmapped_required_fields": {
      -      "type": "array"
      -    },
      -    "warnings": {
      -      "type": "array"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "abi_type_coercions": {
      +      "items": {
      +        "properties": {
      +          "abi_input": {
      +            "type": "string"
      +          },
      +          "coercion": {
      +            "type": "string"
      +          },
      +          "iso_field": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "draft_pinned": {
      +      "type": "boolean"
      +    },
      +    "field_bindings": {
      +      "items": {
      +        "properties": {
      +          "abi_input": {
      +            "type": "string"
      +          },
      +          "iso_field": {
      +            "type": "string"
      +          },
      +          "resolved": {
      +            "type": "boolean"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "iso_message_type": {
      +      "type": "string"
      +    },
      +    "mapping_ok": {
      +      "type": "boolean"
      +    },
      +    "mapping_profile": {
      +      "type": "string"
      +    },
      +    "mapping_profile_version": {
      +      "type": "string"
      +    },
      +    "resolved_call": {
      +      "properties": {
      +        "args": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "function": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "unmapped_required_fields": {
      +      "type": "array"
      +    },
      +    "warnings": {
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: server-side vs browser compute delegation by gpu flag, transient processing with no storage or logging, determinism, and an AP2 export carrying execution_hash for chain provenance. That is real context beyond the annotations, though it never explains failure behavior (mapping_ok=false, unmapped_required_fields, warnings) in practical terms.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening repeats the tool title and then says 'compute node' twice ('OpenChainGraph compute node (compliance_mandate). Deterministic OpenChainGraph compute node.'), and the text buries the actual purpose behind a URL, an FV-status hash path, and a trailing self-referential 'Output schema: call describe_tool(...)'. Much of this boilerplate is identical across sibling tools and displaces the one sentence an agent needs first.

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?

With no output schema, the description does list the return fields (abi_type_coercions, field_bindings, resolved_call, unmapped_required_fields, mapping_ok, warnings), which is valuable. But it leaves the meaning of mapping_profile / iso_fields / contract_abi_fragment and the semantics of a failed mapping undescribed, so an agent still lacks enough to predict outcomes for a non-trivial nested-object tool.

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 the schema already documents compute, parent_hashes, parent_tool_ids and policy_parameters, including the required policy keys. The description's compute-mode explanation largely restates the schema's own compute description and adds no meaning to the parent_hashes/parent_tool_ids chaining or the policy_parameters semantics, so 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 core sentence — 'Deterministic bind of an ISO 20022 pacs.008 ... or pacs.009 ... to EVM contract-call arguments, plus an OCG receipt of the mapping' — names a specific verb, input resource and output artifact, and enumerates the resolution outputs. It does not, however, differentiate from adjacent siblings such as validate_pacs008_party_completeness or map_mt9xx_to_camt beyond a single downstream pointer ('Output feeds: art-291-screen-onledger-transfer-batch').

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 rather than stated: the tool is for binding pacs.008/pacs.009 messages to EVM calldata, and the description warns 'Use synthetic or anonymised inputs only'. There is no explicit when-to-use versus when-not, no stated prerequisites (e.g. a mapping_profile and contract_abi_fragment must be supplied), and no routing advice among the many ISO 20022 siblings.

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.