Skip to main content
Glama

Ariadne Nexus Provenance & Underwriting MCP

Ed25519 Zero-PII Provenance Proof & Optical Score Generator

generate_zk_provenance_proof
Read-onlyIdempotent

Computes a 0x01-prefixed SHA-256 custodial Merkle root, optical microtopography score (7200-9985 bps), underwriting recommendation, and Ed25519-signed ZK_PROV_V1 zero-PII provenance certificate. Use when: generating a pre-bind title attestation for an asset_id and policy_ref from custodial SHA-256 digests. Do not use when: verifying an existing certificate (use verify_zk_provenance_proof instead) or sizing multi-asset portfolio loans (use batch_underwrite_portfolio instead). Behavior: Read-only attestation (p99=380ms; $2.50 USD / 250 cents via X-API-Key or X-Payment; returns an 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": {
      "asset_id": "<asset_id>",
      "policy_ref": "<policy_ref>"
    },
    "name": "generate_zk_provenance_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYesUnique alphanumeric collateral or vault asset identifier, 3-64 chars allowing underscores, colons, or hyphens (e.g., "art_vault_basquiat_09").
policy_refYesUnderwriting binder or specialty title policy reference ID, 3-64 chars (e.g., "POL-CHUBB-2026-441").
optical_scan_sha256NoOptional 64-character hex SHA-256 digest of the raking-light or XRF optical microtopography scan; derived from asset_id when omitted.
custody_event_hashesNoOrdered list of up to 128 SHA-256 hex digests of prior custodial transfers folded into the 0x01 Merkle root; defaults to a genesis leaf if empty.

Output Schema

NameRequiredDescriptionDefault
tierYesCommercial execution tier ("gated_production").
toolYesExecuted tool identifier ("generate_zk_provenance_proof").
asset_idYesAttested collateral identifier.
policy_refYesBound underwriting policy or binder reference.
custody_chain_depthYesNumber of custodial transfer leaves folded into the Merkle tree.
execution_latency_msYesServer-side execution duration in milliseconds.
optical_forensic_score_bpsYesSurface microtopography concordance score in basis points (7200-9985).
zk_attestation_certificateYesEd25519-signed ZK_PROV_V1 zero-PII attestation envelope.
underwriting_recommendationYesDeterministic specialty-title bind recommendation.
title_lien_clearance_merkle_rootYes0x-prefixed 64-hex SHA-256 Merkle root with 0x01 internal node separation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / asset_id / description
      Added value: +"Unique alphanumeric collateral or vault asset identifier, 3-64 chars allowing underscores, colons, or hyphens (e.g., \"art_vault_basquiat_09\")."
    • addedInput schema / properties / asset_id / maxLength
      Added value: +64
    • addedInput schema / properties / asset_id / minLength
      Added value: +3
    • addedInput schema / properties / asset_id / pattern
      Added value: +"^[a-zA-Z0-9_:-]{3,64}$"
    • addedInput schema / properties / custody_event_hashes
      Added value: +{
      +  "default": [],
      +  "description": "Ordered list of up to 128 SHA-256 hex digests of prior custodial transfers folded into the 0x01 Merkle root; defaults to a genesis leaf if empty.",
      +  "items": {
      +    "description": "64-character hex SHA-256 digest of a chronological custodial transfer event (zero seller PII).",
      +    "pattern": "^(?:0x)?[a-fA-F0-9]{64}$",
      +    "type": "string"
      +  },
      +  "maxItems": 128,
      +  "type": "array"
      +}
    • addedInput schema / properties / optical_scan_sha256
      Added value: +{
      +  "description": "Optional 64-character hex SHA-256 digest of the raking-light or XRF optical microtopography scan; derived from asset_id when omitted.",
      +  "pattern": "^(?:0x)?[a-fA-F0-9]{64}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / policy_ref / description
      Added value: +"Underwriting binder or specialty title policy reference ID, 3-64 chars (e.g., \"POL-CHUBB-2026-441\")."
    • addedInput schema / properties / policy_ref / maxLength
      Added value: +64
    • addedInput schema / properties / policy_ref / minLength
      Added value: +3
    • addedInput schema / properties / policy_ref / pattern
      Added value: +"^[a-zA-Z0-9_:-]{3,64}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "asset_id": {
      +      "description": "Attested collateral identifier.",
      +      "type": "string"
      +    },
      +    "custody_chain_depth": {
      +      "description": "Number of custodial transfer leaves folded into the Merkle tree.",
      +      "type": "integer"
      +    },
      +    "execution_latency_ms": {
      +      "description": "Server-side execution duration in milliseconds.",
      +      "type": "number"
      +    },
      +    "optical_forensic_score_bps": {
      +      "description": "Surface microtopography concordance score in basis points (7200-9985).",
      +      "type": "integer"
      +    },
      +    "policy_ref": {
      +      "description": "Bound underwriting policy or binder reference.",
      +      "type": "string"
      +    },
      +    "tier": {
      +      "description": "Commercial execution tier (\"gated_production\").",
      +      "type": "string"
      +    },
      +    "title_lien_clearance_merkle_root": {
      +      "description": "0x-prefixed 64-hex SHA-256 Merkle root with 0x01 internal node separation.",
      +      "type": "string"
      +    },
      +    "tool": {
      +      "description": "Executed tool identifier (\"generate_zk_provenance_proof\").",
      +      "type": "string"
      +    },
      +    "underwriting_recommendation": {
      +      "description": "Deterministic specialty-title bind recommendation.",
      +      "enum": [
      +        "BIND_ELIGIBLE_STANDARD",
      +        "BIND_WITH_ENHANCED_DEDUCTIBLE"
      +      ],
      +      "type": "string"
      +    },
      +    "zk_attestation_certificate": {
      +      "description": "Ed25519-signed ZK_PROV_V1 zero-PII attestation envelope.",
      +      "properties": {
      +        "issued_at_utc": {
      +          "description": "ISO-8601 UTC attestation issuance timestamp.",
      +          "type": "string"
      +        },
      +        "oracle_pubkey_ed25519_b64": {
      +          "description": "Base64-encoded 32-byte Ed25519 oracle public key.",
      +          "type": "string"
      +        },
      +        "public_statement": {
      +          "description": "Pipe-delimited ZK_PROV_V1 signed public claims.",
      +          "type": "string"
      +        },
      +        "scheme": {
      +          "description": "Attestation signature scheme (\"ariadne-zk-ed25519-v1\").",
      +          "type": "string"
      +        },
      +        "seller_pii_exposed": {
      +          "description": "Always false; confirms zero seller PII in public claims.",
      +          "type": "boolean"
      +        },
      +        "signature_b64": {
      +          "description": "Base64-encoded 64-byte Ed25519 signature over public_statement.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "scheme",
      +        "public_statement",
      +        "oracle_pubkey_ed25519_b64",
      +        "signature_b64",
      +        "issued_at_utc",
      +        "seller_pii_exposed"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "tool",
      +    "tier",
      +    "asset_id",
      +    "policy_ref",
      +    "title_lien_clearance_merkle_root",
      +    "custody_chain_depth",
      +    "optical_forensic_score_bps",
      +    "underwriting_recommendation",
      +    "zk_attestation_certificate",
      +    "execution_latency_ms"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, and the description is consistent with them ('Read-only attestation'). Beyond that, it adds real operational context: p99 latency (~380ms), cost ($2.50 USD / 250 cents), auth methods (X-API-Key or X-Payment), and the unbilled 402 quote behavior when unentitled. That is exactly the kind of billing/entitlement context annotations cannot express.

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?

Structure is front-loaded and scannable: outputs first, then 'Use when', 'Do not use when', then 'Behavior'. Every sentence carries information, though the opening sentence is heavily jargon-dense and packs four distinct outputs into one clause, which costs some readability.

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, the description need not document return shape, yet it still names the key artifacts (Merkle root, optical score range, recommendation, certificate). Combined with usage routing, cost/auth, and latency, an agent has everything needed to select and invoke 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 each of the four parameters already carries a detailed description including patterns, examples, and defaults. The tool description only alludes to the required inputs generically ('an asset_id and policy_ref from custodial SHA-256 digests') without adding meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb-plus-resource statement ('Computes a 0x01-prefixed SHA-256 custodial Merkle root, optical microtopography score... Ed25519-signed ZK_PROV_V1 zero-PII provenance certificate'), which tells an agent exactly what is produced. It is clearly distinguished from `verify_zk_provenance_proof` and `batch_underwrite_portfolio` by name.

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?

Explicit 'Use when' clause names the precondition (agenerating a pre-bind title attestation for an asset_id and policy_ref from custodial SHA-256 digests'). The 'Do not use when' clause names two alternatives and the conditions that select them (verification vs. generating, single-asset vs. portfolio sizing). No inference is required.

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