Skip to main content
Glama

AINumbers Fintech Intelligence Suite

Securitization Risk Retention Check

check_securitization_risk_retention
Read-onlyIdempotent

Securitization Risk Retention Check: 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. Open at: https://ainumbers.co/chaingraph/art-447-securitization-risk-retention-check.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: EU Securitisation Regulation (EU) 2017/2402 Art.6 and U.S. Outputs: actual_retention_pct, breach_reasons, compliant, jurisdiction, note, qrm_exemption_applied, regulatory_basis, required_retention_pct, retained_amount_musd, retained_interest_hedged_or_sold, retainer_is_sole_purpose_entity, retention_method, retention_method_valid, total_securitized_exposure_musd. Output schema: call describe_tool("check_securitization_risk_retention").

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

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: all_exposures_qrm_qualified, jurisdiction, retained_interest_hedged_or_sold, retainer_is_sole_purpose_entity, retention_method. 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: all_exposures_qrm_qualified, jurisdiction, retained_interest_hedged_or_sold, retainer_is_sole_purpose_entity, retention_method. Unknown keys are refused."
    • addedInput schema / properties / policy_parameters / properties
      Added value: +{
      +  "all_exposures_qrm_qualified": {
      +    "type": "boolean"
      +  },
      +  "jurisdiction": {},
      +  "retained_amount_musd": {
      +    "type": "number"
      +  },
      +  "retained_interest_hedged_or_sold": {
      +    "type": "boolean"
      +  },
      +  "retainer_is_sole_purpose_entity": {
      +    "type": "boolean"
      +  },
      +  "retention_method": {},
      +  "total_securitized_exposure_musd": {
      +    "type": "number"
      +  }
      +}
    • removedInput schema / properties / policy_parameters / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "actual_retention_pct": {
      -      "type": "integer"
      -    },
      -    "breach_reasons": {
      -      "type": "array"
      -    },
      -    "compliant": {
      -      "type": "boolean"
      -    },
      -    "jurisdiction": {
      -      "type": "string"
      -    },
      -    "note": {
      -      "type": "string"
      -    },
      -    "qrm_exemption_applied": {
      -      "type": "boolean"
      -    },
      -    "regulatory_basis": {
      -      "type": "string"
      -    },
      -    "required_retention_pct": {
      -      "type": "integer"
      -    },
      -    "retained_amount_musd": {
      -      "type": "integer"
      -    },
      -    "retained_interest_hedged_or_sold": {
      -      "type": "boolean"
      -    },
      -    "retainer_is_sole_purpose_entity": {
      -      "type": "boolean"
      -    },
      -    "retention_method": {
      -      "type": "string"
      -    },
      -    "retention_method_valid": {
      -      "type": "boolean"
      -    },
      -    "total_securitized_exposure_musd": {
      -      "type": "integer"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "actual_retention_pct": {
      +      "type": "integer"
      +    },
      +    "breach_reasons": {
      +      "type": "array"
      +    },
      +    "compliant": {
      +      "type": "boolean"
      +    },
      +    "jurisdiction": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "qrm_exemption_applied": {
      +      "type": "boolean"
      +    },
      +    "regulatory_basis": {
      +      "type": "string"
      +    },
      +    "required_retention_pct": {
      +      "type": "integer"
      +    },
      +    "retained_amount_musd": {
      +      "type": "integer"
      +    },
      +    "retained_interest_hedged_or_sold": {
      +      "type": "boolean"
      +    },
      +    "retainer_is_sole_purpose_entity": {
      +      "type": "boolean"
      +    },
      +    "retention_method": {
      +      "type": "string"
      +    },
      +    "retention_method_valid": {
      +      "type": "boolean"
      +    },
      +    "total_securitized_exposure_musd": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Added

TDQS

C2.9/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, but the description adds real context beyond them: deterministic execution, the auto/server/browser compute binding and when delegation occurs, transient non-retained processing, and an AP2 artifact carrying execution_hash for chain provenance. The FV-status snapshot note further clarifies that the verification receipt works offline. It does not describe failure modes or breach-reporting behavior, keeping it below 5.

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 text opens with several sentences of platform boilerplate (compute binding, Workers, AP2 artifacts) before the purpose, and the single sentence that should state what the tool does is cut off mid-clause. The output-field list is defensible given no output schema, but the front-loading is inverted and the truncated summary wastes the most valuable slot.

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?

Because there is no output schema, enumerating the returned fields (compliant, breach_reasons, actual vs required_retention_pct, qrm_exemption_applied) is genuinely useful, and the compute/retention mechanics are covered. But the substantive side is incomplete: the regulatory basis sentence is truncated, and jurisdiction and retention_method — the two inputs that drive the decision — are untyped, unenumerated, and unexplained in both schema and description.

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 documentation and baseline 3 applies. The description restates the compute-mode semantics and the list of required policy_parameters keys, but adds no meaning beyond the schema — notably it never explains what values jurisdiction or retention_method accept, even though both are schema-empty objects with no type or enum.

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

Purpose3/5

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

The title and name establish that this is a securitization risk-retention compliance check, and the description anchors it to EU Securitisation Regulation 2017/2402 Art.6. However, the actual purpose sentence is truncated ("...Art.6 and U.S."), so the description never states what the check computes (comparing retained amount against a required minimum) or how it differs from the many other check_* compliance siblings.

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 guidance and no named alternative among siblings such as check_safeguarding_reconciliation or check_capital_adequacy_private. The only usage-adjacent instruction is the input constraint "Use synthetic or anonymised inputs only," which governs data handling rather than tool selection.

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.