AINumbers Fintech Intelligence Suite

Royalty Split Validator

validate_royalty_split

Read-onlyIdempotent

Royalty Split Validator: 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. Open at: https://ainumbers.co/chaingraph/art-208-royalty-split-validator.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: Validates on-chain royalty split configurations against ERC-2981 (single-receiver) and 0xSplits (multi-recipient) rules. Outputs: cap_bps, config_hash, disclaimer, mode, recipient_count, rules, sum, valid. Output schema: call describe_tool("validate_royalty_split").

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: cap_bps, config, entries. 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: cap_bps, config, entries. Unknown keys are refused."

addedInput schema / properties / policy_parameters / properties

Added value: +{
+  "cap_bps": {},
+  "config": {},
+  "entries": {
+    "type": "array"
+  }
+}

removedInput schema / properties / policy_parameters / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "cap_bps": {
-      "type": "number"
-    },
-    "config_hash": {
-      "type": "string"
-    },
-    "disclaimer": {
-      "type": "string"
-    },
-    "mode": {
-      "enum": [
-        "bps",
-        "percent"
-      ],
-      "type": "string"
-    },
-    "recipient_count": {
-      "type": "number"
-    },
-    "rules": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "detail": {
-            "type": "string"
-          },
-          "id": {
-            "type": "string"
-          },
-          "label": {
-            "type": "string"
-          },
-          "pass": {
-            "enum": [
-              false,
-              true
-            ],
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "detail",
-          "id",
-          "label",
-          "pass"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "sum": {
-      "type": "number"
-    },
-    "valid": {
-      "enum": [
-        false,
-        true
-      ],
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "cap_bps",
-    "config_hash",
-    "disclaimer",
-    "mode",
-    "recipient_count",
-    "rules",
-    "sum",
-    "valid"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "cap_bps": {
+      "type": "number"
+    },
+    "config_hash": {
+      "type": "string"
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "mode": {
+      "enum": [
+        "bps",
+        "percent"
+      ],
+      "type": "string"
+    },
+    "recipient_count": {
+      "type": "number"
+    },
+    "rules": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "detail": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "label": {
+            "type": "string"
+          },
+          "pass": {
+            "enum": [
+              false,
+              true
+            ],
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "detail",
+          "id",
+          "label",
+          "pass"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "sum": {
+      "type": "number"
+    },
+    "valid": {
+      "enum": [
+        false,
+        true
+      ],
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "cap_bps",
+    "config_hash",
+    "disclaimer",
+    "mode",
+    "recipient_count",
+    "rules",
+    "sum",
+    "valid"
+  ],
+  "type": "object"
+}

AddedJul 3, 2026

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, but the description adds real behavioral context beyond them: server-side Cloudflare Workers execution, browser delegation for gpu:true nodes, transient non-retained input processing, and an AP2 artifact export with execution_hash for provenance. The 'Unknown keys are refused' note in the policy_parameters schema is the only validation-failure behavior mentioned, and no contradiction with annotations exists.

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 single most important sentence — what the tool validates — sits at the very end after OpenChainGraph branding, compute-node mechanics, a privacy notice, and a long FV-status URL and hash. Several sentences describe platform infrastructure rather than this tool, and the ordering actively delays the purpose.

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?

It enumerates the output fields (cap_bps, config_hash, mode, recipient_count, rules, sum, valid) despite there being no output schema, and covers compute-mode and privacy behavior. What is missing is the meaning of the policy_parameters inputs and any statement of what makes a split invalid, which an agent needs to call this correctly.

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 restates the compute:"auto" default and browser delegation but adds no new meaning for the policy_parameters sub-keys (cap_bps, config, entries) that drive the actual validation.

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 Summary sentence names a specific verb and resource ("Validates on-chain royalty split configurations") and scopes it to ERC-2981 single-receiver and 0xSplits multi-recipient rules, which separates it from sibling calculate_erc2981_royalty. However this purpose statement arrives only after several sentences of infrastructure boilerplate, so the tool's identity is not front-loaded.

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?

It gives a data-handling caution ("Use synthetic or anonymised inputs only") and explains the compute-mode choice, but never says when to pick this validator over calculate_erc2981_royalty or when a split config is out of scope. Usage is implied by the validation framing rather than stated.

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.

Royalty Split Validator

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources