Skip to main content
Glama

AINumbers Fintech Intelligence Suite

by co.ainumbers
OverviewDiscussionsAdmin

Halt + Staleness Collateral Haircut

compute_stock_token_collateral_haircut
Read-onlyIdempotent

Halt + Staleness Collateral Haircut: OpenChainGraph compute node (collateral_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: 505-tokenized-collateral-eligibility-checker, 508-repo-haircut-collateral-calculator. Open at: https://ainumbers.co/chaingraph/art-320-rhc-collateral-haircut.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: Layers a feed-staleness, sequencer-downtime, and underlying-halt haircut on top of a base repo haircut for Robinhood Chain stock tokens posted as collateral. Outputs: adjusted_collateral_value, base_haircut, extra_haircut, feed_stale, final_haircut, liquidation_risk, sequencer_down_grace_expired, sequencer_down_within_grace, underlying_halted, verdict. Output schema: call describe_tool("compute_stock_token_collateral_haircut").

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". 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\". Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
+  "base_haircut": {},
+  "current_time": {},
+  "feed_round": {},
+  "position_value": {},
+  "sequencer_uptime": {},
+  "underlying_market_state": {}
+}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
-  "type": "string"
-}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "adjusted_collateral_value": {
-      "type": "integer"
-    },
-    "base_haircut": {
-      "type": "number"
-    },
-    "extra_haircut": {
-      "type": "integer"
-    },
-    "feed_stale": {
-      "type": "boolean"
-    },
-    "final_haircut": {
-      "type": "number"
-    },
-    "liquidation_risk": {
-      "type": "string"
-    },
-    "sequencer_down_grace_expired": {
-      "type": "boolean"
-    },
-    "sequencer_down_within_grace": {
-      "type": "boolean"
-    },
-    "underlying_halted": {
-      "type": "boolean"
-    },
-    "verdict": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "adjusted_collateral_value": {
+      "type": "integer"
+    },
+    "base_haircut": {
+      "type": "number"
+    },
+    "extra_haircut": {
+      "type": "integer"
+    },
+    "feed_stale": {
+      "type": "boolean"
+    },
+    "final_haircut": {
+      "type": "number"
+    },
+    "liquidation_risk": {
+      "type": "string"
+    },
+    "sequencer_down_grace_expired": {
+      "type": "boolean"
+    },
+    "sequencer_down_within_grace": {
+      "type": "boolean"
+    },
+    "underlying_halted": {
+      "type": "boolean"
+    },
+    "verdict": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  5. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses compute mode behavior (server-side vs browser delegation, gpu:true handling), transient data processing with no storage or logging, the requirement for synthetic or anonymised inputs, AP2 artifact export with execution_hash, upstream artifact chaining, and FV-status snapshot semantics. This is rich behavioral context that an agent cannot infer from annotations alone.

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 the output list is useful, but the description is dense and contains repetition ('OpenChainGraph compute node' appears twice), boilerplate about compute binding that duplicates the schema, and an embedded URL plus long FV-status path. It is serviceable for a complex tool but not lean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description explicitly enumerates the returned fields (adjusted_collateral_value, base_haircut, extra_haircut, feed_stale, final_haircut, liquidation_risk, sequencer_down_grace_expired, sequencer_down_within_grace, underlying_halted, verdict). It also covers compute modes, provenance chaining, transient data handling, and upstream artifact sources, leaving an agent with enough to call and interpret the tool 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 all parameters are already documented in the input schema. The description echoes the compute-mode semantics already present in the schema and gives no additional per-parameter guidance for parent_hashes, parent_tool_ids, or policy_parameters, so the baseline 3 is appropriate.

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

Purpose5/5

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

The description states a specific computation—layering feed-staleness, sequencer-downtime, and underlying-halt haircuts on a base repo haircut for Robinhood Chain stock tokens posted as collateral. It distinguishes this from the base repo haircut function by naming the upstream artifacts it consumes and the exact extra risk factors it adds.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context: use when computing collateral haircuts for Robinhood Chain stock tokens needing halt/staleness/sequencer adjustments, building on a base repo haircut and consuming artifacts from two named upstream tools. It does not explicitly state when not to use this versus related siblings such as calculate_repo_haircut, but the scope is otherwise unambiguous.

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 toolsInspect
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.

Resources