Skip to main content
Glama

FORUM Merkle proof

get_proof
Read-onlyIdempotent

Return the Merkle audit path that ties one FORUM trust record to the daily release root: leaf, index (0-based leaf position), path (sibling hashes, leaf level first) and root. Same object as GET /v1/trust/{registry_name}/proof on the FORUM HTTP API. Verification recipe: (1) h = the 32 bytes of leaf (hex-decoded; leaf is the record's content_sha256), i = index. (2) For each hex sibling s in path, in order: if i is even, h = sha256(h + s_bytes); if i is odd, h = sha256(s_bytes + h); then i = i // 2. (3) hex(h) must equal root. Then compare root with merkle_root from get_method and with the on-chain anchor (method doc section 10.2); a root taken only from this response shows internal consistency, not publication. A valid proof shows that the record is part of the published release; it says nothing about whether the scored server is safe. A score is: Not a security guarantee, not a penetration test, not certification of code correctness. An unknown name returns isError with error=not_in_registry. Read-only.

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": {
      "registry_name": "<registry_name>"
    },
    "name": "get_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
registry_nameYesMCP Registry server name, exactly as the registry spells it: owner/name, e.g. io.github.pipeworx-io/19hz. Contains a slash; pass it raw (no URL-encoding). Case-sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnly/idempotent annotations, it discloses the error path ('unknown name returns isError with error=not_in_registry'), the exact algorithmic verification steps with hash ordering rules, and the critical limitation that a root from this response alone shows internal consistency, not publication. It also scopes the claim (no statement about server safety, not a security guarantee or certification).

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 output shape is front-loaded and the numbered recipe is well structured with no filler in the core. There is mild redundancy near the end where 'says nothing about whether the scored server is safe' is restated as 'not a security guarantee, not a penetration test, not certification'.

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 no output schema, the description carries the return contract itself (leaf, index, path, root) and explains what each means and how to consume it. Error behavior, upstream root sources, and interpretability limits are all covered for a one-parameter tool.

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% and the single parameter is fully documented there, including the owner/name format and case sensitivity. The description only indirectly touches the parameter via the not_in_registry error; per the baseline rule for high coverage, a 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 first sentence gives a precise verb and resource ('Return the Merkle audit path that ties one FORUM trust record to the daily release root') and enumerates the returned fields. It also names the sibling get_method as the source of the merkle_root to compare against, so an agent can distinguish the two roles 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 Guidelines4/5

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

The verification recipe and the statement that 'a valid proof shows the record is part of the published release' make the intended use case (proof verification) explicit, and get_method is named for the root comparison. It stops short of explicit when-not guidance or routing away from trust_lookup for other query types.

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.