Skip to main content
Glama

Ariadne Nexus Provenance & Underwriting MCP

Underwriting LTV Cap & Oracle Root-of-Trust Verifier

verify_underwriting_compliance
Read-onlyIdempotent

Audits a portfolio underwriting summary against the ANX-RFC-001 55% (5500 bps) Merton stressed advance cap, classifies optical forensic score thresholds, and returns the active ZK_PROV_V1 Ed25519 oracle public key and SHA-256 fingerprint. Use when: validating credit-committee LTV compliance on a batch_underwrite_portfolio quote or retrieving the oracle public key for pinning in verify_zk_provenance_proof. Do not use when: computing stressed collateral values from raw asset schedules (use batch_underwrite_portfolio instead), verifying an Ed25519 certificate signature (use verify_zk_provenance_proof instead), or checking JSON manifest fields (use inspect_manifest_schema instead). Behavior: Read-only, stateless compliance check (p99=15ms; free discovery tier at 60 RPM without billing).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "portfolio_id": "<portfolio_id>",
      "total_appraised_value_cents": "<total_appraised_value_cents>",
      "total_merton_stressed_value_cents": "<total_merton_stressed_value_cents>",
      "proposed_advance_cents": "<proposed_advance_cents>"
    },
    "name": "verify_underwriting_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
portfolio_idYesPortfolio or credit facility identifier audited for statutory LTV compliance (e.g., "port_fine_art_2026_q4").
proposed_advance_centsYesProposed loan advance in exact integer USD cents tested against the ANX-RFC-001 55% (5500 bps) Merton stressed advance ceiling.
total_appraised_value_centsYesAggregate appraised portfolio value in exact integer USD cents (>= 1).
min_optical_forensic_score_bpsNoMinimum item-level optical forensic score across the portfolio in basis points (0-10000; default: 8500).
total_merton_stressed_value_centsYesAggregate Merton 99% tail-stressed liquidation value in integer USD cents returned by batch_underwrite_portfolio.

Output Schema

NameRequiredDescriptionDefault
tierYesCommercial execution tier ("free_discovery").
toolYesExecuted tool identifier ("verify_underwriting_compliance").
compliantYesTrue when proposed_advance_cents <= 55% of stressed value, stressed value <= appraised value, and min_optical_forensic_score_bps >= 8000.
portfolio_idYesAudited portfolio or credit facility identifier.
gross_ltv_bpsYesProposed advance divided by total appraised value in basis points.
headroom_centsYesSigned integer USD cents remaining under ceiling (negative indicates cap breach).
stressed_ltv_bpsYesProposed advance divided by Merton 99% stressed value in basis points.
optical_policy_tierYesUnderwriting policy tier determined by min_optical_forensic_score_bps.
oracle_trust_anchorYesActive ANX-RFC-001 Ed25519 oracle root-of-trust metadata for key pinning.
execution_latency_msYesServer-side execution duration in milliseconds.
max_compliant_advance_centsYesMaximum ANX-RFC-001 compliant loan advance in integer USD cents (5500 bps of stressed value).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world traits, and the description goes further with statelessness, p99=15ms latency, and the 60 RPM free discovery tier with no billing. It also discloses that the tool returns the active ZK_PROV_V1 Ed25519 public key and SHA-256 fingerprint, which is behavior not derivable from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then segments 'Use when', 'Do not use when' and 'Behavior' so an agent can scan quickly. It is dense with domain jargon and long for a single paragraph, but nearly every clause carries operational information rather than repetition.

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?

Given an output schema exists, return values need not be spelled out, yet the description still flags the oracle key and fingerprint as outputs. Combined with the cap rule, the required-parameter workflow and the sibling routing, an agent has everything needed to select and call it correctly.

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 every parameter including the min_optical_forensic_score_bps default is already documented in the schema. The description reinforces the 5500 bps cap and the provenance of total_merton_stressed_value_cents from batch_underwrite_portfolio, but adds little syntax or semantic detail beyond structured data, so the baseline 3 applies.

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?

States a specific verb ('Audits') plus the exact resource and rule set ('portfolio underwriting summary against the ANX-RFC-001 55% (5500 bps) Merton stressed advance cap'), and additionally names the secondary oracle-key retrieval. The dual function is clearly delineated and distinguishable from siblings like verify_zk_provenance_proof and batch_underwrite_portfolio.

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

Usage Guidelines5/5

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

Contains an explicit 'Use when' clause tied to concrete workflows (credit-committee LTV validation on a batch_underwrite_portfolio quote, oracle key pinning) and a 'Do not use when' clause routing three named alternatives to their correct tools. Nothing is left to inference.

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.

Resources