Skip to main content
Glama

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

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": "validate_royalty_split"
  }
}

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: cap_bps, config, entries. 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: 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"
      -}
  3. Changed1 schema field changed
    • 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
  4. Changed1 schema field changed
    • 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"
      +}
  5. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is lower. The description still adds real behavior: deterministic computation, transient processing with no storage or logging, browser delegation URL fallback, and an AP2 artifact export with execution_hash for provenance. That is meaningful context beyond the structured fields.

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 definition opens with vendor infrastructure detail (Cloudflare Workers, gpu:false kernels) and an inline FV-status URL with a 64-character hash before reaching the actual purpose. Roughly half the text is boilerplate that does not help an agent decide or invoke, and the actionable summary is back-loaded.

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 tool with a nested policy_parameters object and no output schema, the description does supply the output field list (cap_bps, config_hash, mode, recipient_count, rules, sum, valid) and the privacy posture. What it omits is what makes a split invalid and how cap_bps/entries interact, but the 100%-covered schema carries most of that.

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 the compute-mode semantics verbatim without adding anything, and says nothing about cap_bps, config, or entries beyond noting the export chain fields. 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 summary sentence states a specific verb and resource: validates on-chain royalty split configurations against ERC-2981 (single-receiver) and 0xSplits (multi-recipient) rules. That distinguishes it reasonably from calculate_erc2981_royalty, though it never names that sibling explicitly. The purpose is clear but buried after several sentences of infrastructure boilerplate.

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?

The description gives conditional guidance on compute modes (auto vs browser vs gpu:true delegation) and a hard input constraint ('use synthetic or anonymised inputs only'). It never says when to reach for this tool rather than a sibling validator or calculator, so tool selection is left to inference.

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.