Skip to main content
Glama

Ariadne Nexus Provenance & Underwriting MCP

Collateral Manifest Schema & Field Validator

inspect_manifest_schema
Read-onlyIdempotent

Returns required ANX-RFC-001 (ZK_PROV_V1) manifest fields for a collateral class and validates an optional candidate manifest object, listing missing keys and attestation readiness. Use when: checking required manifest keys or pre-validating a candidate JSON payload before SHA-256 hashing. Do not use when: validating an existing 64-hex SHA-256 digest (use verify_asset_hash instead), signing a provenance certificate (use generate_zk_provenance_proof instead), or auditing portfolio LTV caps (use verify_underwriting_compliance instead). Behavior: Read-only, stateless, deterministic schema check (p99=28ms; free discovery tier at 60 RPM without billing).

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

Input Schema

NameRequiredDescriptionDefault
collateral_classNoSpecialty collateral category whose ANX-RFC-001 manifest schema is inspected (default: "fine_art").fine_art
manifest_payloadNoOptional candidate collateral manifest JSON object validated for required ANX-RFC-001 keys (asset_id, collateral_class, optical_scan_sha256, custody_event_hashes, appraised_value_cents). Omit to list required fields only.

Output Schema

NameRequiredDescriptionDefault
tierYesCommercial execution tier ("free_discovery").
toolYesExecuted tool identifier ("inspect_manifest_schema").
missing_fieldsYesRequired manifest keys absent from manifest_payload.
payload_checkedYesTrue when a candidate manifest_payload object was supplied.
collateral_classYesEvaluated specialty collateral classification.
execution_latency_msYesServer-side execution duration in milliseconds.
ready_for_zk_attestationYesTrue when manifest_payload was supplied and missing_fields is empty.
required_manifest_fieldsYesRequired ANX-RFC-001 top-level manifest keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / collateral_class / default
      Added value: +"fine_art"
    • addedInput schema / properties / collateral_class / description
      Added value: +"Specialty collateral category whose ANX-RFC-001 manifest schema is inspected (default: \"fine_art\")."
    • addedInput schema / properties / collateral_class / enum
      Added value: +[
      +  "fine_art",
      +  "rwa_bullion",
      +  "rare_manuscript",
      +  "collectible"
      +]
    • addedInput schema / properties / manifest_payload
      Added value: +{
      +  "description": "Optional candidate collateral manifest JSON object validated for required ANX-RFC-001 keys (asset_id, collateral_class, optical_scan_sha256, custody_event_hashes, appraised_value_cents). Omit to list required fields only.",
      +  "type": "object"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "collateral_class": {
      +      "description": "Evaluated specialty collateral classification.",
      +      "enum": [
      +        "fine_art",
      +        "rwa_bullion",
      +        "rare_manuscript",
      +        "collectible"
      +      ],
      +      "type": "string"
      +    },
      +    "execution_latency_ms": {
      +      "description": "Server-side execution duration in milliseconds.",
      +      "type": "number"
      +    },
      +    "missing_fields": {
      +      "description": "Required manifest keys absent from manifest_payload.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "payload_checked": {
      +      "description": "True when a candidate manifest_payload object was supplied.",
      +      "type": "boolean"
      +    },
      +    "ready_for_zk_attestation": {
      +      "description": "True when manifest_payload was supplied and missing_fields is empty.",
      +      "type": "boolean"
      +    },
      +    "required_manifest_fields": {
      +      "description": "Required ANX-RFC-001 top-level manifest keys.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "tier": {
      +      "description": "Commercial execution tier (\"free_discovery\").",
      +      "type": "string"
      +    },
      +    "tool": {
      +      "description": "Executed tool identifier (\"inspect_manifest_schema\").",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "tool",
      +    "tier",
      +    "collateral_class",
      +    "required_manifest_fields",
      +    "payload_checked",
      +    "missing_fields",
      +    "ready_for_zk_attestation",
      +    "execution_latency_ms"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description nonetheless adds non-obvious operational context: stateless, deterministic, p99=28ms, and a free discovery tier at 60 RPM without billing. It does not describe response shape, but an output schema exists so that burden is lifted.

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-loaded with the core action, then clearly segmented into 'Use when', 'Do not use when', and 'Behavior'. Nearly every clause carries information, though the latency and rate-limit figures sit in a single trailing sentence that is more operational trivia than selection criteria.

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?

With rich annotations, an output schema, 100% schema description coverage, and a nested optional object, the remaining risk is misrouting to a sibling, which the description handles explicitly. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100%, so both parameters are already documented, including the enum and the default for collateral_class. The description echoes the 'optional candidate manifest object' framing and the listing-only mode but adds no syntax, format, or constraint detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 specific verbs and resources: returns required ANX-RFC-001 (ZK_PROV_V1) manifest fields for a collateral class and validates an optional candidate manifest object. It also names the concrete outputs (missing keys, attestation readiness), which lets an agent distinguish it from verify_asset_hash or generate_zk_provenance_proof without opening either 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?

Explicit 'Use when' clauses cover both modes (listing required keys, pre-validating a payload before SHA-256 hashing), and 'Do not use when' names three alternatives with the specific condition that routes to each. 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