Skip to main content
Glama
Sign In
certified-mcp

certified-mcp

by nickharris808
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

verify_receipt

Verify logic-equivalence receipts by re-running DRAT proof checks, re-simulating counterexamples, and recomputing hash chains to re-derive verdicts from committed artifacts.

Instructions

Verify a logic-equivalence receipt. Re-runs the DRAT proof check (or re-simulates the counterexample) over the committed formula, and recomputes the hash chain. The verdict is re-derived, never read from the receipt.

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": {
      "receipt_path": "<receipt_path>"
    },
    "name": "verify_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
receipt_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the DRAT check is re-run, the counterexample is re-simulated, and the hash chain is recomputed, emphasizing that the verdict is re-derived rather than read from the receipt. This builds trust without needing annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences front-load the purpose, then add process details, and finally emphasize the trust model. No filler or redundancy.

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?

The tool has one parameter and no output schema, but the description does not state what the tool returns (e.g., a verdict) or how the result is presented. It also lacks guidance on how this differs from sibling tools, leaving some gaps given the complex domain of proof verification.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the only parameter, receipt_path, is not explained in the description. The description refers to 'the receipt' but never clarifies what the path should point to or any constraints, leaving the parameter semantics to the name alone.

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 'Verify a logic-equivalence receipt,' which is a specific verb and resource. It clearly distinguishes from siblings like verify_certificate by focusing on receipts, and adds details about re-running DRAT proof checks and recomputing hash chains.

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?

The description implies when to use the tool (when you have a receipt to verify) but does not explicitly contrast it with alternatives like check_drat or verify_certificate. No when-not-to-use guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools