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/ca4e1dca8343f788a296161f0e19712f7afb7e5eaec0431081e715a4cc34b784.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").

Input Schema

Name	Required	Description
`compute`	No	Compute 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_hashes`	No	execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export).
`parent_tool_ids`	No	tool_id values matching parent_hashes, in the same order.
`policy_parameters`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed3 schema fields changedOct 19, 2026

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"
-}
```

Changed1 schema field changedSep 18, 2026

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

Changed1 schema field changedSep 3, 2026

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"
+}

AddedJul 13, 2026

TDQS

B3.2/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 closed-world behavior. The description adds meaningful context beyond that: server-side vs browser compute routing, gpu:true always delegating, transient processing with no storage/logging, synthetic-input-only policy, and AP2 artifact export with execution_hash.

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 core purpose is buried after redundant phrasing ('OpenChainGraph compute node' repeated) and before link/FV-status metadata. Several sentences do not assist tool selection, and the useful summary would be stronger if front-loaded; the definition is unnecessarily long for the information it conveys.

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?

For a 4-parameter compute tool with no output schema, the description supplies key context: compute routing, privacy constraints, artifact provenance, and a list of output fields. It could say more about return value shape, but annotations and the schema already cover safety and inputs.

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. The description repeats compute-mode semantics and required policy keys but adds no format examples or coercion rules for the nested policy_parameters fields, making the baseline 3 appropriate.

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 states a specific verb-resource pair: deterministic bind of an ISO 20022 pacs.008/pacs.009 message to EVM contract-call arguments, plus a receipt of the mapping. It does not explicitly contrast with sibling tools, so the agent must infer scope from the wording rather than from a direct sibling comparison.

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 explicit when-to-use guidance or named alternative. The only routing note is 'Output feeds: art-291-screen-onledger-transfer-batch', while the compute-mode discussion explains parameter behavior rather than when to choose this tool over siblings like validate_pacs008_party_completeness or screen_onledger_transfer_batch.

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

All AINumbers Fintech Intelligence Suite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

ISO 20022-to-EVM Calldata Mapper

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources