Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Basel 3.1 Reporting Delta Calculator

compute_basel31_delta
Read-onlyIdempotent

Basel 3.1 Reporting Delta Calculator: OpenChainGraph compute node (capital_assessment). Regulatory deadline: 2027-01-01 (UK PRA PS1/26 Basel 3.1 go-live — January 1, 2027). 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: sim-03-basel-rwa-scenario-modeler, ptg-01-ap2-prompt-template-generator. Open at: https://ainumbers.co/chaingraph/art-07-basel31-reporting-delta-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.

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": "compute_basel31_delta"
  }
}

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". See the tool's manifest for field names.

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
    • addedInput schema / properties / compute
      Added value: +{
      +  "description": "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.",
      +  "enum": [
      +    "auto",
      +    "server",
      +    "browser"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / inputs
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "Simulation parameters for this tool's input fields. See the tool's embedded manifest for field names.",
      -  "propertyNames": {
      -    "type": "string"
      -  },
      -  "type": "object"
      -}
    • addedInput schema / properties / policy_parameters
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "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.",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  3. Added

TDQS

C2.9/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses determinism, default Cloudflare Workers execution, browser delegation and its URL response, GPU behavior, transient input handling, and the synthetic-or-anonymised-input restriction. It also explains AP2 execution_hash provenance and the snapshot/offline-verification semantics of the FV receipt, providing substantial operational, privacy, and provenance context.

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 dense paragraph repeats the title, OpenChainGraph node label, and regulatory date, then devotes considerable space to infrastructure, URLs, and a long receipt hash. Although several operational details are valuable, the actual calculation is not front-loaded and the schema-duplicated compute guidance could be substantially shortened.

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

Completeness2/5

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

It usefully describes execution behavior, the AP2 artifact, provenance, and downstream feeds, which is especially helpful because there is no output schema. It remains insufficient for confident domain invocation: the delta's baseline and target, required financial inputs and their formats or units, and the meaning of the computed result are all absent.

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 coverage is 100%, and the description mostly repeats the schema's compute auto/browser rules while adding execution-location and input-handling context. It does not identify the domain-specific members of policy_parameters, whose schema defers to an external manifest, or add further meaning for the parent hash and tool ID parameters.

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

Purpose2/5

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

The opening largely restates the title and labels the node as capital_assessment, but never explains which reporting states or measures are compared to produce the delta. The UK PRA reference narrows the regulatory setting without clarifying the computation or distinguishing it from Basel comparison and RWA-related siblings.

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?

The UK go-live date, capital-assessment category, and named downstream nodes imply use within a Basel 3.1 implementation and provenance workflow. However, there is no explicit when-to-use condition or comparison with alternatives such as compare_basel_2023_vs_2026 or compute_rwa_scenarios.

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.