Skip to main content
Glama

Ariadne Nexus Provenance & Underwriting MCP

Collateral SHA-256 Digest & Commitment Verifier

verify_asset_hash
Read-onlyIdempotent

Validates and normalizes a 64-character hexadecimal SHA-256 collateral manifest digest and derives its deterministic specialty-title registry commitment ID (cmt_*) for fine art, bullion, manuscripts, or collectibles. Use when: confirming manifest SHA-256 digest conformance and commitment binding prior to paid underwriting. Do not use when: checking unhashed JSON manifest fields (use inspect_manifest_schema instead) or verifying a signed ZK_PROV_V1 certificate (use verify_zk_provenance_proof instead). Behavior: Read-only, stateless, deterministic computation (p99=42ms; free discovery tier at 30 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": {
      "asset_sha256": "<asset_sha256>"
    },
    "name": "verify_asset_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_sha256Yes64-character hexadecimal SHA-256 digest of the canonical collateral manifest JSON, with optional 0x prefix (e.g., "0x9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08").
collateral_classNoSpecialty collateral classification bound into the cmt_* registry commitment ID (default: "fine_art").fine_art

Output Schema

NameRequiredDescriptionDefault
tierYesCommercial execution tier ("free_discovery").
toolYesExecuted tool identifier ("verify_asset_hash").
manifest_sha256YesNormalized lowercase 0x-prefixed 64-hex SHA-256 digest.
collateral_classYesBound specialty collateral classification.
execution_latency_msYesServer-side execution duration in milliseconds.
registry_commitment_idYesDeterministic specialty-title commitment identifier prefixed with cmt_.
locked_production_fieldsYesGated attestation fields unlocked via generate_zk_provenance_proof.
schema_conformance_validYesTrue when the digest conforms to ANX-RFC-001 32-byte SHA-256 rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / asset_sha256 / description
      Added value: +"64-character hexadecimal SHA-256 digest of the canonical collateral manifest JSON, with optional 0x prefix (e.g., \"0x9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08\")."
    • addedInput schema / properties / asset_sha256 / pattern
      Added value: +"^(?:0x)?[a-fA-F0-9]{64}$"
    • addedInput schema / properties / collateral_class / default
      Added value: +"fine_art"
    • addedInput schema / properties / collateral_class / description
      Added value: +"Specialty collateral classification bound into the cmt_* registry commitment ID (default: \"fine_art\")."
    • addedInput schema / properties / collateral_class / enum
      Added value: +[
      +  "fine_art",
      +  "rwa_bullion",
      +  "rare_manuscript",
      +  "collectible"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "collateral_class": {
      +      "description": "Bound 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"
      +    },
      +    "locked_production_fields": {
      +      "description": "Gated attestation fields unlocked via generate_zk_provenance_proof.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "manifest_sha256": {
      +      "description": "Normalized lowercase 0x-prefixed 64-hex SHA-256 digest.",
      +      "type": "string"
      +    },
      +    "registry_commitment_id": {
      +      "description": "Deterministic specialty-title commitment identifier prefixed with cmt_.",
      +      "type": "string"
      +    },
      +    "schema_conformance_valid": {
      +      "description": "True when the digest conforms to ANX-RFC-001 32-byte SHA-256 rules.",
      +      "type": "boolean"
      +    },
      +    "tier": {
      +      "description": "Commercial execution tier (\"free_discovery\").",
      +      "type": "string"
      +    },
      +    "tool": {
      +      "description": "Executed tool identifier (\"verify_asset_hash\").",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "tool",
      +    "tier",
      +    "manifest_sha256",
      +    "collateral_class",
      +    "schema_conformance_valid",
      +    "registry_commitment_id",
      +    "locked_production_fields",
      +    "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 readOnly/idempotent/non-destructive/closed-world, and the description still adds real context beyond them: stateless deterministic computation, p99 latency of 42ms, and a free discovery tier at 30 RPM without billing. Those operational traits (cost, rate limit, performance) are exactly what an agent needs before calling.

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?

The Use when / Do not use when / Behavior structure is easy to scan and front-loads the core action. The opening sentence is dense and packs four asset classes plus the commitment derivation, but no sentence is wasted.

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 an output schema present, return values need not be explained, and the description covers purpose, exclusions, determinism, cost, and rate limits. Nothing an agent needs to invoke this two-parameter read-only tool 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 description coverage is 100%, so both parameters (asset_sha256 with its pattern and example, collateral_class with its enum and default) are already fully documented. The description adds only the notion of normalization and the class-to-commitment binding, which the schema largely restates, so the baseline of 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?

The description opens with a specific verb and resource: validates/normalizes a 64-character hex SHA-256 collateral manifest digest and derives a cmt_* commitment ID. It scopes the asset classes (fine art, bullion, manuscripts, collectibles) and is clearly distinguishable from the sibling verifiers named later.

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 ties invocation to confirming digest conformance and commitment binding before paid underwriting. The 'Do not use when' clause names two concrete alternatives (inspect_manifest_schema for unhashed JSON fields, verify_zk_provenance_proof for ZK_PROV_V1 certificates), so routing is unambiguous.

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