Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Supervisory Scenario Replay (DFAST-lite)

replay_supervisory_scenario
Read-onlyIdempotent

Supervisory Scenario Replay (DFAST-lite): OpenChainGraph compute node (capital_assessment). Regulatory deadline: 2027-02-01 (Annual re-pin — Fed publishes new supervisory scenarios each February). 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-01-lcr-nsfr-liquidity-stress-test, sim-03-basel-rwa-scenario-modeler. Open at: https://ainumbers.co/chaingraph/art-370-supervisory-scenario-replay.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: Replays the Fed's published 2026 28-variable supervisory scenario paths (baseline and severely adverse, Q1:2026-Q1:2029) against user-supplied loss and PPNR coefficient functions, producing a quarterly P&L and capital walk. Outputs: ending_capital_mn, not_a_submission, quarters, scenario, scenario_release_date, scenario_set_digest, scenario_source_url, starting_capital_mn, trough_capital_mn, trough_capital_ratio_pct, trough_quarter. Output schema: call describe_tool("replay_supervisory_scenario").

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

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: loss_function, ppnr_function, quarterly_distribution_mn, rwa_mn, scenario, starting_capital_mn, tax_rate. 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: loss_function, ppnr_function, quarterly_distribution_mn, rwa_mn, scenario, starting_capital_mn, tax_rate. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "loss_function": {},
      +  "ppnr_function": {},
      +  "quarterly_distribution_mn": {},
      +  "rwa_mn": {},
      +  "scenario": {},
      +  "starting_capital_mn": {},
      +  "tax_rate": {}
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "ending_capital_mn": {
      -      "type": "number"
      -    },
      -    "not_a_submission": {
      -      "type": "string"
      -    },
      -    "quarters": {
      -      "items": {
      -        "properties": {
      -          "capital_mn": {
      -            "type": "number"
      -          },
      -          "capital_ratio_pct": {
      -            "type": "number"
      -          },
      -          "date": {
      -            "type": "string"
      -          },
      -          "loss_mn": {
      -            "type": "integer"
      -          },
      -          "net_income_mn": {
      -            "type": "number"
      -          },
      -          "ppnr_mn": {
      -            "type": "number"
      -          },
      -          "pretax_income_mn": {
      -            "type": "number"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "scenario": {
      -      "type": "string"
      -    },
      -    "scenario_release_date": {
      -      "type": "string"
      -    },
      -    "scenario_set_digest": {
      -      "type": "string"
      -    },
      -    "scenario_source_url": {
      -      "type": "string"
      -    },
      -    "starting_capital_mn": {
      -      "type": "integer"
      -    },
      -    "trough_capital_mn": {
      -      "type": "integer"
      -    },
      -    "trough_capital_ratio_pct": {
      -      "type": "number"
      -    },
      -    "trough_quarter": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "ending_capital_mn": {
      +      "type": "number"
      +    },
      +    "not_a_submission": {
      +      "type": "string"
      +    },
      +    "quarters": {
      +      "items": {
      +        "properties": {
      +          "capital_mn": {
      +            "type": "number"
      +          },
      +          "capital_ratio_pct": {
      +            "type": "number"
      +          },
      +          "date": {
      +            "type": "string"
      +          },
      +          "loss_mn": {
      +            "type": "integer"
      +          },
      +          "net_income_mn": {
      +            "type": "number"
      +          },
      +          "ppnr_mn": {
      +            "type": "number"
      +          },
      +          "pretax_income_mn": {
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scenario": {
      +      "type": "string"
      +    },
      +    "scenario_release_date": {
      +      "type": "string"
      +    },
      +    "scenario_set_digest": {
      +      "type": "string"
      +    },
      +    "scenario_source_url": {
      +      "type": "string"
      +    },
      +    "starting_capital_mn": {
      +      "type": "integer"
      +    },
      +    "trough_capital_mn": {
      +      "type": "integer"
      +    },
      +    "trough_capital_ratio_pct": {
      +      "type": "number"
      +    },
      +    "trough_quarter": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses compute-mode behavior, GPU delegation, transient input processing with no storage or logging, synthetic-input requirements, deterministic execution, AP2 artifact provenance, and the fact that the output is not a regulatory submission. These are substantive behavioral details that an agent could not infer from readOnlyHint and idempotentHint alone.

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 core purpose is buried after a title repetition, a regulatory deadline, compute-node metadata, and a long URL/FV-status hash block; the actual summary appears only near the end. Several sentences duplicate the schema, and the description is longer and less front-loaded than needed for an agent to select and invoke the tool.

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?

There is no output schema, but the description lists the returned fields, explains the artifact and provenance behavior, and covers compute and privacy constraints. For a complex financial replay tool, this is enough for an agent to understand what the call produces and how it behaves.

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 explains compute, parent_hashes, parent_tool_ids, and policy_parameters. The description adds useful context by identifying loss and PPNR coefficient functions as inputs, but it largely repeats the compute-mode explanation already present in the schema and does not deepen parent-hash or policy-parameter semantics.

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 verb and resource: replaying the Fed's published 2026 28-variable supervisory scenario paths against user-supplied loss and PPNR coefficient functions to produce a quarterly P&L and capital walk. The DFAST-lite framing, scenario scope, and named outputs distinguish it from generic stress-test 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?

It gives regulatory context and says the output feeds two named simulation tools, which implies when the tool is relevant. However, it does not explicitly state when to choose this tool over siblings such as compute_stress_test_scenarios or run_liquidity_stress_test, nor does it provide exclusions or prerequisites.

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.