AINumbers Fintech Intelligence Suite

Publish Index Head

publish_index_head

Read-onlyIdempotent

Publish Index Head: OpenChainGraph compute node (attestation_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. Consumes upstream artifacts from: art-646-compile-rebalance-evidence-pack, art-647-record-index-correction. Open at: https://ainumbers.co/chaingraph/art-658-publish-index-head.html FV-status (published/proven/still-trusted for this spec): /fv-status/8498d0819c941fdb731f9e10f5d93ee929026919cb111a42149821b48b5ac180.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Output schema: call describe_tool("publish_index_head").

Input Schema

TableJSON 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". See the tool's manifest for field names.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "chain_errors": {
-      "type": "array"
-    },
-    "chain_valid": {
-      "type": [
-        "null",
-        "boolean"
-      ]
-    },
-    "chain_verified_by": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "errors": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "fence": {
-      "type": "string"
-    },
-    "head_hash": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "is_genesis": {
-      "enum": [
-        false,
-        true
-      ],
-      "type": "boolean"
-    },
-    "not_proven": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "detail": {
-            "type": "string"
-          },
-          "item": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "detail",
-          "item"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "prev_head_hash": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "regulatory_framework": {
-      "type": "string"
-    },
-    "root": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "rotates_to": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "seq": {
-      "type": [
-        "null",
-        "number"
-      ]
-    },
-    "signature_valid": {
-      "type": [
-        "null",
-        "boolean"
-      ]
-    },
-    "signature_verified_by": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "signer": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "stream": {
-      "type": [
-        "null",
-        "string"
-      ]
-    },
-    "structural_error": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "timestamp": {
-      "type": [
-        "null",
-        "string"
-      ]
-    }
-  },
-  "required": [
-    "chain_errors",
-    "chain_valid",
-    "chain_verified_by",
-    "errors",
-    "fence",
-    "head_hash",
-    "is_genesis",
-    "not_proven",
-    "prev_head_hash",
-    "regulatory_framework",
-    "root",
-    "rotates_to",
-    "seq",
-    "signature_valid",
-    "signature_verified_by",
-    "signer",
-    "stream",
-    "structural_error",
-    "timestamp"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "chain_errors": {
+      "type": "array"
+    },
+    "chain_valid": {
+      "type": [
+        "null",
+        "boolean"
+      ]
+    },
+    "chain_verified_by": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "errors": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "fence": {
+      "type": "string"
+    },
+    "head_hash": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "is_genesis": {
+      "enum": [
+        false,
+        true
+      ],
+      "type": "boolean"
+    },
+    "not_proven": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "detail": {
+            "type": "string"
+          },
+          "item": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "detail",
+          "item"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "prev_head_hash": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "regulatory_framework": {
+      "type": "string"
+    },
+    "root": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "rotates_to": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "seq": {
+      "type": [
+        "null",
+        "number"
+      ]
+    },
+    "signature_valid": {
+      "type": [
+        "null",
+        "boolean"
+      ]
+    },
+    "signature_verified_by": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "signer": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "stream": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "structural_error": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timestamp": {
+      "type": [
+        "null",
+        "string"
+      ]
+    }
+  },
+  "required": [
+    "chain_errors",
+    "chain_valid",
+    "chain_verified_by",
+    "errors",
+    "fence",
+    "head_hash",
+    "is_genesis",
+    "not_proven",
+    "prev_head_hash",
+    "regulatory_framework",
+    "root",
+    "rotates_to",
+    "seq",
+    "signature_valid",
+    "signature_verified_by",
+    "signer",
+    "stream",
+    "structural_error",
+    "timestamp"
+  ],
+  "type": "object"
+}

AddedAug 29, 2026

TDQS

A3.6/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 reconciles the 'publish' verb with them by explaining that inputs are processed transiently and not stored, logged, or retained. It also discloses non-obvious routing behavior: compute:'browser' returns a browser delegation URL, gpu:true nodes always delegate, and the output is an AP2 artifact carrying execution_hash. Error handling and failure modes are not covered.

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

Conciseness3/5

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

The scoping and compute-mode information is front-loaded, but the description opens with a redundant restatement ('Publish Index Head: OpenChainGraph compute node' followed immediately by 'Deterministic OpenChainGraph compute node') and spends significant space on a long FV-status hash URL and provenance prose. Several sentences are dense jargon that could be tightened.

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?

With no output schema, the description carries the return burden and does describe the artifact output (AP2 artifact with execution_hash) and the browser-delegation URL case, and it points to describe_tool for the output schema. Given four parameters including a nested object, it is reasonably complete, missing only failure/edge behavior.

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 mostly restates the compute enum rather than adding syntax or semantics, though naming the upstream artifacts gives some meaning to the parent-hash chaining inputs. Baseline 3 is 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 ('Publish Index Head', a deterministic compute node that exports an AP2 artifact with execution_hash for chain provenance), so the agent knows the outcome. However, it never distinguishes this from close siblings like publish_fund_nav_head, publish_market_mark_head, or publish_model_risk_head, and the first sentences drift into compute-node jargon rather than the index-head semantics.

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 prerequisites indirectly by naming the upstream artifacts it consumes (art-646-compile-rebalance-evidence-pack, art-647-record-index-correction) and a hard constraint ('Use synthetic or anonymised inputs only'). But it never says when to choose this tool over alternatives such as record_index_correction or emit_chaingraph_artifact, leaving usage largely inferred.

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.

Publish Index Head

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources