AINumbers Fintech Intelligence Suite

Parametric Trigger Payout Calculator

compute_parametric_trigger_payout

Read-onlyIdempotent

Parametric Trigger Payout Calculator: 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. Output feeds: art-252-validate-cat-bond-trigger-terms. Open at: https://ainumbers.co/chaingraph/art-251-compute-parametric-trigger-payout.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: Evaluates parametric insurance triggers and computes payout amounts. Outputs: anchor_surface, coverage_amount, index_value, not_legal_advice, parametric_limit, payout_amount, pii_note, regulatory_basis, table_source, table_version, threshold_used, tier_matched_index, trigger_fraction, trigger_hit, trigger_receipt, trigger_type_used. Output schema: call describe_tool("compute_parametric_trigger_payout").

Input 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". Required: coverage_amount, index_value, max_index, parametric_limit, threshold, tier_table, trigger_type. Unknown keys are refused.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed3 schema fields changedOct 19, 2026

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: coverage_amount, index_value, max_index, parametric_limit, threshold, tier_table, trigger_type. Unknown keys are refused."

addedInput schema / properties / policy_parameters / properties

Added value: +{
+  "coverage_amount": {},
+  "index_value": {},
+  "max_index": {},
+  "parametric_limit": {},
+  "threshold": {},
+  "tier_table": {
+    "type": "array"
+  },
+  "trigger_type": {}
+}

removedInput schema / properties / policy_parameters / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "anchor_surface": {
-      "type": "string"
-    },
-    "coverage_amount": {
-      "type": "integer"
-    },
-    "index_value": {
-      "type": "integer"
-    },
-    "not_legal_advice": {
-      "type": "string"
-    },
-    "parametric_limit": {
-      "type": "integer"
-    },
-    "payout_amount": {
-      "type": "integer"
-    },
-    "pii_note": {
-      "type": "string"
-    },
-    "regulatory_basis": {
-      "type": "string"
-    },
-    "table_source": {
-      "type": "string"
-    },
-    "table_version": {
-      "type": "string"
-    },
-    "threshold_used": {
-      "type": "integer"
-    },
-    "tier_matched_index": {
-      "type": "string"
-    },
-    "trigger_fraction": {
-      "type": "integer"
-    },
-    "trigger_hit": {
-      "type": "boolean"
-    },
-    "trigger_receipt": {
-      "properties": {
-        "coverage_amount": {
-          "type": "integer"
-        },
-        "index_value": {
-          "type": "integer"
-        },
-        "max_index_used": {
-          "type": "string"
-        },
-        "parametric_limit": {
-          "type": "integer"
-        },
-        "payout_amount": {
-          "type": "integer"
-        },
-        "threshold_used": {
-          "type": "integer"
-        },
-        "tier_matched_index": {
-          "type": "string"
-        },
-        "trigger_fraction": {
-          "type": "integer"
-        },
-        "trigger_hit": {
-          "type": "boolean"
-        },
-        "trigger_type": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "trigger_type_used": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "anchor_surface": {
+      "type": "string"
+    },
+    "coverage_amount": {
+      "type": "integer"
+    },
+    "index_value": {
+      "type": "integer"
+    },
+    "not_legal_advice": {
+      "type": "string"
+    },
+    "parametric_limit": {
+      "type": "integer"
+    },
+    "payout_amount": {
+      "type": "integer"
+    },
+    "pii_note": {
+      "type": "string"
+    },
+    "regulatory_basis": {
+      "type": "string"
+    },
+    "table_source": {
+      "type": "string"
+    },
+    "table_version": {
+      "type": "string"
+    },
+    "threshold_used": {
+      "type": "integer"
+    },
+    "tier_matched_index": {
+      "type": "string"
+    },
+    "trigger_fraction": {
+      "type": "integer"
+    },
+    "trigger_hit": {
+      "type": "boolean"
+    },
+    "trigger_receipt": {
+      "properties": {
+        "coverage_amount": {
+          "type": "integer"
+        },
+        "index_value": {
+          "type": "integer"
+        },
+        "max_index_used": {
+          "type": "string"
+        },
+        "parametric_limit": {
+          "type": "integer"
+        },
+        "payout_amount": {
+          "type": "integer"
+        },
+        "threshold_used": {
+          "type": "integer"
+        },
+        "tier_matched_index": {
+          "type": "string"
+        },
+        "trigger_fraction": {
+          "type": "integer"
+        },
+        "trigger_hit": {
+          "type": "boolean"
+        },
+        "trigger_type": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "trigger_type_used": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJul 5, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real value by disclosing the compute-mode split (server kernel vs browser delegation URL for gpu:true), the transient-processing/no-logging retention policy, and the AP2 artifact with execution_hash. It does not cover latency, rate limits, or failure modes of the delegation path.

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 redundant name restatement ('Parametric Trigger Payout Calculator: OpenChainGraph compute node... Deterministic OpenChainGraph compute node') and includes a long URL plus an FV-status hash and snapshot disclaimer that do not help an agent decide or invoke. The genuinely useful purpose statement and output list appear only after this preamble.

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?

All four parameters are documented, the required policy_parameters keys are enumerated, the full output field list is given (no output schema exists, so this compensates), and the downstream chaining target is named. Missing: what a trigger_hit=false result looks like operationally and how to handle the browser delegation response.

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% and the compute-mode text in the description largely restates the enum's own documentation. The policy_parameters required-key list and 'unknown keys are refused' note are useful but also present in the schema. Baseline 3 applies since the schema carries the semantics.

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: 'Evaluates parametric insurance triggers and computes payout amounts', plus a concrete output list (payout_amount, trigger_hit, tier_matched_index). It also names the downstream consumer, validate_cat_bond_trigger_terms, which helps separate it from validation-only siblings. It loses a point because the actual purpose sentence is buried after infrastructure boilerplate rather than front-loaded.

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?

Usage is implied through the upstream/downstream chain hint ('Output feeds: art-252-validate-cat-bond-trigger-terms') and the synthetic-inputs-only constraint. There is no explicit statement of when to choose this over alternatives such as derive_parametric_index_from_receipts or validate_cat_bond_trigger_terms. The agent must infer the workflow position.

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.

Parametric Trigger Payout Calculator

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources