AINumbers Fintech Intelligence Suite

Publish Model Risk Head

publish_model_risk_head

Read-onlyIdempotent

Publish Model Risk 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-453-model-validation-status, art-489-model-test-battery, art-562-compile-model-risk-lineage-pack. Open at: https://ainumbers.co/chaingraph/art-649-publish-model-risk-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_model_risk_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"
-      ]
-    },
-    "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",
-    "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"
+      ]
+    },
+    "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",
+    "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 18, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral facts: deterministic execution, transient processing with no storage/logging/retention, the compute:auto vs browser delegation split, and the fact that a browser delegation URL is returned instead of a result. The offline-verifiable FV-status receipt is extra provenance context. It stops short of describing rate limits or failure modes.

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 purpose is front-loaded, and some content (transient processing, synthetic inputs) earns its place, but the description is a dense wall of jargon that repeats the compute-binding rules already in the schema and injects a raw URL and a 64-character hash that disrupt readability.

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 does the work of explaining the returned AP2 artifact and execution_hash, and it points to describe_tool for the output contract. Given full schema coverage, annotations, and named upstream dependencies, an agent has nearly everything needed to call it; only the internal structure of policy_parameters remains opaque.

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 all four parameters are already documented in the schema and this is the baseline case. The description's compute-mode explanation largely repeats the schema text, and for the opaque policy_parameters object it defers to an external manifest ('see the tool's manifest for field names') rather than adding meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is an OpenChainGraph compute node that exports an AP2 artifact with an execution_hash and consumes named upstream artifacts, which is more specific than the title alone. However, it never says plainly what the 'Model Risk Head' is or what decision it produces, and it does not distinguish itself from near-identical siblings such as publish_fund_nav_head, publish_index_head, and publish_market_mark_head.

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 implies usage context by naming the upstream artifacts it chains from (art-453, art-489, art-562) and gives a hard constraint ('use synthetic or anonymised inputs only'), which is genuinely useful. It gives no explicit when-to-use vs when-not-to-use guidance and no routing to alternative publish_* tools.

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 Model Risk Head

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources