Skip to main content
Glama

Mdexa

Get a ledger inclusion proof

get_ledger_proof
Read-onlyIdempotent

Merkle inclusion proof that a dataset's recorded license conclusion (or an evidence snapshot) is in the Mdexa Ledger; verify offline with the open verifier. Not counted as a call.

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": {
      "slug": "<slug>"
    },
    "name": "get_ledger_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoverdict
slugYesDataset slug from search_datasets.
hintsNo
snapshot_idNokind=evidence: e.g. s01 (default: latest).

Output Schema

NameRequiredDescriptionDefault
slugNo
proofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower; the description still adds meaningful context beyond them by disclosing that verification happens offline with an external verifier and that the call is not billed ('Not counted as a call'). It also clarifies the two modes of what can be proven, which 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?

A single dense sentence with the core artifact front-loaded, followed by the alternative verification path and a cost note. Every clause carries information; the semicolon-separated structure reads cleanly, though the phrasing is compressed enough to require a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value explanation is unnecessary, and the safety profile is covered by annotations. The gaps are the undocumented 'hints' parameter and the absence of any statement about behavior when no proof can be produced for the requested slug or snapshot.

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 only 50%, and the description compensates partially by explaining the verdict-vs-evidence distinction that drives the 'kind' parameter. However, the 'hints' parameter with its on/off enum is left entirely unexplained in both schema and description, and 'slug' and 'snapshot_id' rely wholly on the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific artifact (a Merkle inclusion proof) over a specific resource (a dataset's recorded license conclusion or an evidence snapshot) in the Mdexa Ledger, which is concrete and distinguishable from a ledger head lookup. It does not explicitly contrast itself with siblings like get_ledger_head or get_license_evidence, so differentiation is left implicit.

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

Usage Guidelines3/5

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

'Verify offline with the open verifier' and 'Not counted as a call' give useful context about how and when to spend this call, which implies it should be preferred over fetching raw data when independent verification is needed. However, there is no explicit statement of when to choose this over get_license_evidence or get_ledger_head, and no guidance on failure cases (e.g., what a proof of absence looks like).

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.