Skip to main content
Glama

AINumbers Fintech Intelligence Suite

IRRBB Basis-Risk NII Shock Calculator

calculate_basis_risk_nii_shock
Read-onlyIdempotent

IRRBB Basis-Risk NII Shock Calculator: OpenChainGraph compute node (analytics_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. Open at: https://ainumbers.co/chaingraph/art-443-irrbb-basis-risk-nii-shock-calculator.html FV-status (published/proven/still-trusted for this spec): /fv-status/565f2dd45a55e0ff0f8dafde8c1080f9e1484b32a5aaa96f4d7739a236b9258a.json — a snapshot, not a subscription; this receipt verifies offline regardless of whether that file is ever fetched. Summary: Comptroller's Handbook IRR basis-risk delta-NII calculator: sweeps a single reference-rate shock across multiple priced indices (Prime, SOFR, Fed Funds, CD portfolio, etc.), each with a caller-declared historical beta vs the reference rate, and isolates the incremental delta-NII from indices not... Outputs: basis_risk_delta_nii, basis_risk_pct_of_parallel, convention, horizon_months, index_results, is_material, material_threshold_pct, parallel_delta_nii, reference_shock_bps, total_net_exposure, total_nii_contribution. Output schema: call describe_tool("calculate_basis_risk_nii_shock").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_basis_risk_nii_shock"
  }
}

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". Required: horizon_months, index_exposures, material_threshold_pct, reference_shock_bps. 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\". Required: horizon_months, index_exposures, material_threshold_pct, reference_shock_bps. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "horizon_months": {},
      +  "index_exposures": {
      +    "type": "array"
      +  },
      +  "material_threshold_pct": {},
      +  "reference_shock_bps": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "basis_risk_delta_nii": {
      -      "type": "integer"
      -    },
      -    "basis_risk_pct_of_parallel": {
      -      "type": "number"
      -    },
      -    "convention": {
      -      "type": "string"
      -    },
      -    "horizon_months": {
      -      "type": "integer"
      -    },
      -    "index_results": {
      -      "items": {
      -        "properties": {
      -          "asset_balance": {
      -            "type": "integer"
      -          },
      -          "beta_vs_reference": {
      -            "type": "integer"
      -          },
      -          "index_name": {
      -            "type": "string"
      -          },
      -          "index_shock_bps": {
      -            "type": "integer"
      -          },
      -          "liability_balance": {
      -            "type": "integer"
      -          },
      -          "net_exposure": {
      -            "type": "integer"
      -          },
      -          "nii_contribution": {
      -            "type": "integer"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "is_material": {
      -      "type": "boolean"
      -    },
      -    "material_threshold_pct": {
      -      "type": "number"
      -    },
      -    "parallel_delta_nii": {
      -      "type": "integer"
      -    },
      -    "reference_shock_bps": {
      -      "type": "integer"
      -    },
      -    "total_net_exposure": {
      -      "type": "integer"
      -    },
      -    "total_nii_contribution": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "basis_risk_delta_nii": {
      +      "type": "integer"
      +    },
      +    "basis_risk_pct_of_parallel": {
      +      "type": "number"
      +    },
      +    "convention": {
      +      "type": "string"
      +    },
      +    "horizon_months": {
      +      "type": "integer"
      +    },
      +    "index_results": {
      +      "items": {
      +        "properties": {
      +          "asset_balance": {
      +            "type": "integer"
      +          },
      +          "beta_vs_reference": {
      +            "type": "integer"
      +          },
      +          "index_name": {
      +            "type": "string"
      +          },
      +          "index_shock_bps": {
      +            "type": "integer"
      +          },
      +          "liability_balance": {
      +            "type": "integer"
      +          },
      +          "net_exposure": {
      +            "type": "integer"
      +          },
      +          "nii_contribution": {
      +            "type": "integer"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "is_material": {
      +      "type": "boolean"
      +    },
      +    "material_threshold_pct": {
      +      "type": "number"
      +    },
      +    "parallel_delta_nii": {
      +      "type": "integer"
      +    },
      +    "reference_shock_bps": {
      +      "type": "integer"
      +    },
      +    "total_net_exposure": {
      +      "type": "integer"
      +    },
      +    "total_nii_contribution": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: deterministic execution, server-side vs browser delegation semantics, transient non-retained inputs, and an AP2 artifact export carrying execution_hash for chain provenance. Much of it is shared platform boilerplate rather than tool-specific, and the materiality/convention behavior of the output is not explained.

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?

Front-loading is poor: the tool title is restated, then compute-binding, retention, artifact, URL and FV-status hash boilerplate precede the actual purpose, and the substantive summary is truncated mid-sentence ('indices not...'). Several lines (the rendered URL and the 64-character provenance hash) carry no selection value for an agent choosing a tool.

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?

There is no output schema, so enumerating outputs (basis_risk_delta_nii, basis_risk_pct_of_parallel, is_material, etc.) is valuable, and the four required policy_parameters keys are named. However the truncated summary leaves the central concept — what the incremental basis component is measured against — incomplete, and the nested index_exposures array is never specified, which matters for a nested-object tool.

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 carries the parameter burden and baseline 3 applies. The description does add a little meaning — 'single reference-rate shock' maps to reference_shock_bps and 'caller-declared historical beta vs the reference rate' hints at the contents of index_exposures — but it never describes the structure of index_exposures entries or how horizon_months/material_threshold_pct affect the result.

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 core sentence is specific: a Comptroller's Handbook IRR basis-risk delta-NII calculator that sweeps a single reference-rate shock across multiple priced indices with caller-declared betas and isolates incremental delta-NII. That is a clear verb+resource distinguishable from parallel-shock siblings like evaluate_irrbb_sot_nii, though the description never names those siblings directly. The purpose is buried behind four sentences of platform boilerplate before it appears.

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 only implied by the phrase 'isolates the incremental delta-NII' — an agent must infer this is the tool for basis (non-parallel) risk rather than the parallel-shock or EVE variants. No sibling tool is named, no exclusion is stated, and the only explicit guidance given ('use synthetic or anonymised inputs only', compute modes) is generic to the Chaingraph platform, not to this calculation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.