Skip to main content
Glama

AINumbers Fintech Intelligence Suite

CECL Expected Credit Loss & Allowance Calculator

calculate_cecl_ecl_allowance
Read-onlyIdempotent

CECL Expected Credit Loss & Allowance Calculator: OpenChainGraph compute node (credit_assessment). 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-426-cecl-ecl-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: Computes a deterministic CECL (Current Expected Credit Loss, ASC 326) allowance given caller-supplied PD/LGD/EAD curves, segment exposures, and forecast scenario weights, and reconciles the result against the prior period's allowance balance. Outputs: boundary_note, charge_offs_usd, constants_version, delta_vs_required_usd, disambiguation, forecast_weights, method, prior_allowance_balance_usd, provision_expense_usd, reconciled_ending_allowance_usd, reconciliation_balanced, recoveries_usd, segment_count, segments, total_required_allowance_usd. Output schema: call describe_tool("calculate_cecl_ecl_allowance").

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_cecl_ecl_allowance"
  }
}

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: constants_version, forecast_weights, method, segments. 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: constants_version, forecast_weights, method, segments. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "charge_offs_usd": {
      +    "type": "number"
      +  },
      +  "constants_version": {},
      +  "forecast_weights": {
      +    "type": "array"
      +  },
      +  "method": {},
      +  "prior_allowance_balance_usd": {
      +    "type": "number"
      +  },
      +  "recoveries_usd": {
      +    "type": "number"
      +  },
      +  "segments": {
      +    "type": "array"
      +  }
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "boundary_note": {
      -      "type": "string"
      -    },
      -    "charge_offs_usd": {
      -      "type": "integer"
      -    },
      -    "constants_version": {
      -      "type": "string"
      -    },
      -    "delta_vs_required_usd": {
      -      "type": "integer"
      -    },
      -    "disambiguation": {
      -      "type": "string"
      -    },
      -    "forecast_weights": {
      -      "items": {
      -        "properties": {
      -          "scenario": {
      -            "type": "string"
      -          },
      -          "weight": {
      -            "type": "number"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "method": {
      -      "type": "string"
      -    },
      -    "prior_allowance_balance_usd": {
      -      "type": "integer"
      -    },
      -    "provision_expense_usd": {
      -      "type": "integer"
      -    },
      -    "reconciled_ending_allowance_usd": {
      -      "type": "integer"
      -    },
      -    "reconciliation_balanced": {
      -      "type": "boolean"
      -    },
      -    "recoveries_usd": {
      -      "type": "integer"
      -    },
      -    "segment_count": {
      -      "type": "integer"
      -    },
      -    "segments": {
      -      "items": {
      -        "properties": {
      -          "ead_usd": {
      -            "type": "integer"
      -          },
      -          "exposure_balance_usd": {
      -            "type": "integer"
      -          },
      -          "lgd_pct": {
      -            "type": "integer"
      -          },
      -          "remaining_life_years": {
      -            "type": "integer"
      -          },
      -          "scenario_count": {
      -            "type": "integer"
      -          },
      -          "scenarios": {
      -            "items": {
      -              "properties": {
      -                "scenario": {
      -                  "type": "string"
      -                },
      -                "scenario_ecl_usd": {
      -                  "type": "integer"
      -                },
      -                "weight": {
      -                  "type": "number"
      -                }
      -              },
      -              "type": "object"
      -            },
      -            "type": "array"
      -          },
      -          "segment_ecl_usd": {
      -            "type": "integer"
      -          },
      -          "segment_id": {
      -            "type": "string"
      -          }
      -        },
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "total_required_allowance_usd": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "boundary_note": {
      +      "type": "string"
      +    },
      +    "charge_offs_usd": {
      +      "type": "integer"
      +    },
      +    "constants_version": {
      +      "type": "string"
      +    },
      +    "delta_vs_required_usd": {
      +      "type": "integer"
      +    },
      +    "disambiguation": {
      +      "type": "string"
      +    },
      +    "forecast_weights": {
      +      "items": {
      +        "properties": {
      +          "scenario": {
      +            "type": "string"
      +          },
      +          "weight": {
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "method": {
      +      "type": "string"
      +    },
      +    "prior_allowance_balance_usd": {
      +      "type": "integer"
      +    },
      +    "provision_expense_usd": {
      +      "type": "integer"
      +    },
      +    "reconciled_ending_allowance_usd": {
      +      "type": "integer"
      +    },
      +    "reconciliation_balanced": {
      +      "type": "boolean"
      +    },
      +    "recoveries_usd": {
      +      "type": "integer"
      +    },
      +    "segment_count": {
      +      "type": "integer"
      +    },
      +    "segments": {
      +      "items": {
      +        "properties": {
      +          "ead_usd": {
      +            "type": "integer"
      +          },
      +          "exposure_balance_usd": {
      +            "type": "integer"
      +          },
      +          "lgd_pct": {
      +            "type": "integer"
      +          },
      +          "remaining_life_years": {
      +            "type": "integer"
      +          },
      +          "scenario_count": {
      +            "type": "integer"
      +          },
      +          "scenarios": {
      +            "items": {
      +              "properties": {
      +                "scenario": {
      +                  "type": "string"
      +                },
      +                "scenario_ecl_usd": {
      +                  "type": "integer"
      +                },
      +                "weight": {
      +                  "type": "number"
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "segment_ecl_usd": {
      +            "type": "integer"
      +          },
      +          "segment_id": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total_required_allowance_usd": {
      +      "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 and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the computation is deterministic, inputs are processed transiently and not stored or logged, synthetic/anonymised inputs are mandated, and an AP2 artifact with execution_hash is exported for chain provenance, with compute mode controlling server vs browser delegation. That is real behavioral content beyond the annotations, though a large share of the text is repeated platform boilerplate rather than tool-specific disclosure.

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 description is badly front-loaded: the reader wades through 'OpenChainGraph compute node (credit_assessment). Deterministic OpenChainGraph compute node.' and an inline FV-status hash URL before reaching what the tool actually does. A 15-item output list and repeated privacy/compute-mode statements pad the text. Several sentences are redundant restatements, and the informative content is at the end rather than the start.

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?

With no output schema, the description usefully enumerates the return fields (total_required_allowance_usd, provision_expense_usd, reconciled_ending_allowance_usd, reconciliation_balanced, etc.), and it covers compute modes, provenance chaining, and data-handling constraints. What is missing is error/failure behavior and any sense of the numeric conventions or units expected in the PD/LGD/EAD curves, but overall it is sufficient for a deterministic compute node of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning the schema does not: it states which policy_parameters keys are actually required (constants_version, forecast_weights, method, segments) even though the schema declares no required fields, and that unknown keys are refused — a strictness constraint absent from the schema. It also explains compute mode semantics and parent_hashes/parent_tool_ids chaining in prose.

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 summary sentence names a specific verb and resource: computes a deterministic CECL (ASC 326) allowance from caller-supplied PD/LGD/EAD curves, segment exposures and scenario weights, and reconciles it to the prior balance. That is far more specific than the title alone. It does not, however, distinguish this from adjacent siblings such as score_credit_default_risk or compute_rwa_scenarios, and the actual purpose statement is buried after a large block of platform boilerplate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no named alternative among the many credit and allowance siblings. The only routing guidance concerns the compute mode (auto/server/browser) and gpu:true delegation, which is invocation mechanics rather than tool selection. The 'Required: constants_version, forecast_weights, method, segments' line implies prerequisites, but that is the closest thing to usage guidance present.

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.