AINumbers Fintech Intelligence Suite

CCP Default Fund Cover-2 Sizing

size_ccp_default_fund_cover2

Read-onlyIdempotent

CCP Default Fund Cover-2 Sizing: OpenChainGraph compute node (risk_parameter). 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: qfa-03-stress-test-engine. Open at: https://ainumbers.co/chaingraph/art-530-default-fund-cover2-sizing.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("size_ccp_default_fund_cover2").

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: -{
-  "properties": {
-    "as_of": {
-      "type": "string"
-    },
-    "fund_adequate": {
-      "type": "boolean"
-    },
-    "fund_size_display": {
-      "type": "string"
-    },
-    "fund_size_minor_units": {
-      "type": "integer"
-    },
-    "member_count": {
-      "type": "integer"
-    },
-    "note": {
-      "type": "string"
-    },
-    "per_scenario": {
-      "items": {
-        "properties": {
-          "cover2_requirement_display": {
-            "type": "string"
-          },
-          "cover2_requirement_minor_units": {
-            "type": "integer"
-          },
-          "largest": {
-            "properties": {
-              "member_id": {
-                "type": "string"
-              },
-              "stress_loss_minor_units": {
-                "type": "integer"
-              }
-            },
-            "type": "object"
-          },
-          "loss_bps": {
-            "type": "integer"
-          },
-          "member_losses": {
-            "items": {
-              "properties": {
-                "member_id": {
-                  "type": "string"
-                },
-                "stress_loss_minor_units": {
-                  "type": "integer"
-                }
-              },
-              "type": "object"
-            },
-            "type": "array"
-          },
-          "scenario_id": {
-            "type": "string"
-          },
-          "second_largest": {
-            "properties": {
-              "member_id": {
-                "type": "string"
-              },
-              "stress_loss_minor_units": {
-                "type": "integer"
-              }
-            },
-            "type": "object"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "rationale": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "rejected_inputs": {
-      "type": "array"
-    },
-    "scenario_count": {
-      "type": "integer"
-    },
-    "shortfall_display": {
-      "type": "string"
-    },
-    "shortfall_minor_units": {
-      "type": "integer"
-    },
-    "worst_case_cover2_requirement_display": {
-      "type": "string"
-    },
-    "worst_case_cover2_requirement_minor_units": {
-      "type": "integer"
-    },
-    "worst_case_scenario_id": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "as_of": {
+      "type": "string"
+    },
+    "fund_adequate": {
+      "type": "boolean"
+    },
+    "fund_size_display": {
+      "type": "string"
+    },
+    "fund_size_minor_units": {
+      "type": "integer"
+    },
+    "member_count": {
+      "type": "integer"
+    },
+    "note": {
+      "type": "string"
+    },
+    "per_scenario": {
+      "items": {
+        "properties": {
+          "cover2_requirement_display": {
+            "type": "string"
+          },
+          "cover2_requirement_minor_units": {
+            "type": "integer"
+          },
+          "largest": {
+            "properties": {
+              "member_id": {
+                "type": "string"
+              },
+              "stress_loss_minor_units": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          },
+          "loss_bps": {
+            "type": "integer"
+          },
+          "member_losses": {
+            "items": {
+              "properties": {
+                "member_id": {
+                  "type": "string"
+                },
+                "stress_loss_minor_units": {
+                  "type": "integer"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "scenario_id": {
+            "type": "string"
+          },
+          "second_largest": {
+            "properties": {
+              "member_id": {
+                "type": "string"
+              },
+              "stress_loss_minor_units": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "rationale": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "rejected_inputs": {
+      "type": "array"
+    },
+    "scenario_count": {
+      "type": "integer"
+    },
+    "shortfall_display": {
+      "type": "string"
+    },
+    "shortfall_minor_units": {
+      "type": "integer"
+    },
+    "worst_case_cover2_requirement_display": {
+      "type": "string"
+    },
+    "worst_case_cover2_requirement_minor_units": {
+      "type": "integer"
+    },
+    "worst_case_scenario_id": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedAug 4, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds substantive context beyond them: transient processing with no storage/logging/retention, deterministic computation, AP2 artifact export with execution_hash for provenance, and browser-delegation behavior. It does not describe return format or failure modes, keeping it below a 5.

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 content is front-loaded with purpose and then mechanics, but it is a single dense run-on paragraph that packs in a long documentation URL, a 64-character FV-status hash, and a describe_tool pointer, some of which is boilerplate repeated across nodes. Efficient in places, padded in others.

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?

For a 4-parameter, nested-object compute node with no output schema, the description usefully covers compute modes, chaining inputs, artifact export and points to describe_tool for the output schema. Yet the actual computation result and the policy_parameters field names remain undefined, deferred to a manifest the agent cannot see from this text.

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 largely repeats the compute-mode semantics already in the enum description. For the opaque policy_parameters object it defers to 'the tool's manifest for field names' rather than adding meaning, so the baseline 3 applies.

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 opening sentence restates the title and adds only the classification 'OpenChainGraph compute node (risk_parameter)', so the agent learns it is a compute node but not what the Cover-2 sizing calculation actually produces. It names a specific domain resource (CCP default fund cover-2), but there is no sibling differentiation against tools like recompute_ccp_default_waterfall. Purpose is inferable but thin.

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 real operational conditions ('compute:auto' server-side vs 'compute:browser' delegation, gpu:true always delegates, use synthetic inputs only, consumes upstream artifacts from qfa-03-stress-test-engine). However it never states when to choose this tool over an alternative or what preconditions make it applicable, leaving the when/when-not inference to the caller.

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.

CCP Default Fund Cover-2 Sizing

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources