Skip to main content
Glama

Ariadne Nexus Provenance & Underwriting MCP

Batch Merton Jump-Diffusion Portfolio Underwriting Engine

batch_underwrite_portfolio
Read-onlyIdempotent

Computes per-asset optical scores (bps), Merton jump-diffusion 99% stressed values, approved advances in integer USD cents, and effective LTV (bps) across 1-100 collateral items. Use when: sizing a fine-art or RWA credit facility from appraised cent values, optical scan digests, custody depth, and horizon days. Do not use when: signing a single-asset proof (use generate_zk_provenance_proof instead) or auditing an underwriting summary against LTV caps (use verify_underwriting_compliance instead). Behavior: Read-only actuarial solver (p99=910ms; $2.50 USD / 250 cents via X-API-Key or X-Payment; unbilled 402 quote if unentitled).

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>",
      "assets": "<assets>"
    },
    "name": "batch_underwrite_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetsYesList of 1 to 100 specialty collateral items to underwrite under Merton jump-diffusion 99% tail stress.
horizon_daysNoCredit facility tenor and liquidation stress horizon in calendar days from 30 to 1825 (default: 365).
portfolio_idYesInstitutional credit facility or collateral schedule identifier, 3-64 chars (e.g., "port_fine_art_2026_q4").
target_advance_rate_bpsNoRequested gross loan-to-value (LTV) advance rate in integer basis points from 1000 (10.00%) to 8500 (85.00%); defaults to 5000 (50.00%).

Output Schema

NameRequiredDescriptionDefault
tierYesCommercial execution tier ("gated_production").
toolYesExecuted tool identifier ("batch_underwrite_portfolio").
assetsYesPer-asset optical scores, stressed values, and approved cent advances.
asset_countYesNumber of collateral items underwritten.
horizon_daysYesLiquidation stress horizon in calendar days.
portfolio_idYesEvaluated portfolio or credit facility identifier.
execution_latency_msYesServer-side execution duration in milliseconds.
effective_portfolio_ltv_bpsYesPortfolio-level approved advance divided by appraised value in bps.
total_appraised_value_centsYesAggregate appraised portfolio value in integer USD cents.
total_approved_advance_centsYesAggregate approved loan advance in integer USD cents.
total_merton_stressed_value_centsYesAggregate Merton 99% tail-stressed value in integer USD cents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / assets / description
      Added value: +"List of 1 to 100 specialty collateral items to underwrite under Merton jump-diffusion 99% tail stress."
    • addedInput schema / properties / assets / items
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Single collateral item with integer-cent appraisal and optical scan digest.",
      +  "properties": {
      +    "appraised_value_cents": {
      +      "description": "Independent appraised value in exact integer USD cents from 1 to 100000000000 ($1B max; e.g., 500000000 for $5M).",
      +      "maximum": 100000000000,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "asset_id": {
      +      "description": "Unique collateral item identifier, 3-64 chars (e.g., \"col_item_01\").",
      +      "pattern": "^[a-zA-Z0-9_:-]{3,64}$",
      +      "type": "string"
      +    },
      +    "custody_depth": {
      +      "default": 3,
      +      "description": "Verified custodial transfer chain depth (1-100); depth >= 4 lowers title-defect jump intensity lambda from 0.19 to 0.08 (default: 3).",
      +      "maximum": 100,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "optical_scan_sha256": {
      +      "description": "64-character hex SHA-256 digest of the item's optical microtopography scan.",
      +      "pattern": "^(?:0x)?[a-fA-F0-9]{64}$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "asset_id",
      +    "appraised_value_cents",
      +    "optical_scan_sha256"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / assets / maxItems
      Added value: +100
    • addedInput schema / properties / assets / minItems
      Added value: +1
    • addedInput schema / properties / horizon_days
      Added value: +{
      +  "default": 365,
      +  "description": "Credit facility tenor and liquidation stress horizon in calendar days from 30 to 1825 (default: 365).",
      +  "maximum": 1825,
      +  "minimum": 30,
      +  "type": "integer"
      +}
    • addedInput schema / properties / portfolio_id
      Added value: +{
      +  "description": "Institutional credit facility or collateral schedule identifier, 3-64 chars (e.g., \"port_fine_art_2026_q4\").",
      +  "maxLength": 64,
      +  "minLength": 3,
      +  "pattern": "^[a-zA-Z0-9_:-]{3,64}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / target_advance_rate_bps
      Added value: +{
      +  "default": 5000,
      +  "description": "Requested gross loan-to-value (LTV) advance rate in integer basis points from 1000 (10.00%) to 8500 (85.00%); defaults to 5000 (50.00%).",
      +  "maximum": 8500,
      +  "minimum": 1000,
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "assets"
      -]New value: +[
      +  "portfolio_id",
      +  "assets"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "asset_count": {
      +      "description": "Number of collateral items underwritten.",
      +      "type": "integer"
      +    },
      +    "assets": {
      +      "description": "Per-asset optical scores, stressed values, and approved cent advances.",
      +      "items": {
      +        "properties": {
      +          "appraised_value_cents": {
      +            "description": "Item appraised value in integer USD cents.",
      +            "type": "integer"
      +          },
      +          "approved_advance_cents": {
      +            "description": "Item approved advance in integer USD cents (capped at 55% of stressed value).",
      +            "type": "integer"
      +          },
      +          "asset_id": {
      +            "description": "Collateral item ID.",
      +            "type": "string"
      +          },
      +          "merton_99_stressed_value_cents": {
      +            "description": "Item Merton 99% stressed value in integer USD cents.",
      +            "type": "integer"
      +          },
      +          "optical_forensic_score_bps": {
      +            "description": "Item optical concordance score in basis points.",
      +            "type": "integer"
      +          },
      +          "status": {
      +            "description": "Item underwriting disposition.",
      +            "enum": [
      +              "APPROVED",
      +              "MANUAL_FORENSIC_REVIEW"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "asset_id",
      +          "appraised_value_cents",
      +          "optical_forensic_score_bps",
      +          "merton_99_stressed_value_cents",
      +          "approved_advance_cents",
      +          "status"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "effective_portfolio_ltv_bps": {
      +      "description": "Portfolio-level approved advance divided by appraised value in bps.",
      +      "type": "integer"
      +    },
      +    "execution_latency_ms": {
      +      "description": "Server-side execution duration in milliseconds.",
      +      "type": "number"
      +    },
      +    "horizon_days": {
      +      "description": "Liquidation stress horizon in calendar days.",
      +      "type": "integer"
      +    },
      +    "portfolio_id": {
      +      "description": "Evaluated portfolio or credit facility identifier.",
      +      "type": "string"
      +    },
      +    "tier": {
      +      "description": "Commercial execution tier (\"gated_production\").",
      +      "type": "string"
      +    },
      +    "tool": {
      +      "description": "Executed tool identifier (\"batch_underwrite_portfolio\").",
      +      "type": "string"
      +    },
      +    "total_appraised_value_cents": {
      +      "description": "Aggregate appraised portfolio value in integer USD cents.",
      +      "type": "integer"
      +    },
      +    "total_approved_advance_cents": {
      +      "description": "Aggregate approved loan advance in integer USD cents.",
      +      "type": "integer"
      +    },
      +    "total_merton_stressed_value_cents": {
      +      "description": "Aggregate Merton 99% tail-stressed value in integer USD cents.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "tool",
      +    "tier",
      +    "portfolio_id",
      +    "asset_count",
      +    "horizon_days",
      +    "total_appraised_value_cents",
      +    "total_merton_stressed_value_cents",
      +    "total_approved_advance_cents",
      +    "effective_portfolio_ltv_bps",
      +    "assets",
      +    "execution_latency_ms"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description goes beyond that with genuinely new operational facts: p99 latency of 910ms, a $2.50 / 250-cent price, X-API-Key or X-Payment authentication, and a 402 quote when unentitled. Those are non-obvious cost and auth behaviors an agent cannot infer from structured fields.

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?

Organized into three front-loaded labeled segments (what, when/not, behavior) with no filler sentences. It is dense in domain jargon ('optical scores', 'RWA', 'effective LTV') that could slow a first read, which keeps it from a full 5.

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?

An output schema exists, so return values need not be explained, and the description still covers selection criteria, cost, auth, latency, and the collapsing pricing path. Nothing an agent needs to invoke this batch solver correctly is missing.

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 nonetheless echoes the driving inputs (cent values, optical scan digests, custody depth, horizon days) in a single clause, confirming which inputs matter for the computation. It adds little on formats or defaults beyond the schema, which is acceptable here.

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 ('Computes per-asset optical scores, Merton jump-diffusion 99% stressed values, approved advances in integer USD cents, and effective LTV') and pins the scope to '1-100 collateral items'. This is enough for an agent to distinguish it from verify_underwriting_compliance and generate_zk_provenance_proof without opening a schema.

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?

It gives an explicit 'Use when' scenario (sizing a fine-art or RWA credit facility from appraised cent values, scan digests, custody depth, horizon days) and an explicit 'Do not use when' clause naming two alternative tools with the conditions that select them. Routing is fully resolved.

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