Skip to main content
Glama

Get consistency proof

get_consistency_proof
Read-only

RFC 6962 proof that the log of size first is a prefix of the log of size second.

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": {
      "first": "<first>",
      "second": "<second>"
    },
    "name": "get_consistency_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstYesOlder tree size
secondYesNewer tree size

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / first / description
      Added value: +"Older tree size"
    • addedInput schema / properties / second / description
      Added value: +"Newer tree size"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the read-only, closed-world profile is covered. The description contributes the RFC 6962 semantic (a proof of prefix consistency) but omits behavioral facts the agent would want: what happens when `first` > `second`, and what form the returned proof takes.

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 tight clause with zero filler, and the defining property is front-loaded. It is arguably too terse rather than bloated, but it is well-structured and wastes nothing.

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?

This is a simple two-parameter read tool with full schema coverage and annotations, so little is strictly required. However, with no output schema the description could have said what the proof looks like or how to use it, and it never states the implicit constraint that `second` should be at least `first` — a real gap for a proof-verification 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 description coverage is 100% — `first` is already documented as 'Older tree size' and `second` as 'Newer tree size'. The description adds only the relational meaning (first is a prefix of second), which is useful framing but no new syntax, units, or edge-case guidance beyond what the schema states.

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?

Names a specific artifact (a consistency proof per RFC 6962) and defines it formally: proves the log of size `first` is a prefix of the log of size `second`. That is far more precise than a restatement of the name, but it never contrasts itself with the sibling `get_inclusion_proof`, so an agent must know RFC 6962 terminology to separate the two.

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

Usage Guidelines2/5

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

There is no when-to-use, no precondition (e.g. that `second` should be at least `first`), and no reference to the closely related `get_inclusion_proof` sibling. The agent is left to infer from the mathematical definition alone whether this is the right tool for its verification task.

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