Skip to main content
Glama

check_proof

Idempotent

Have qed.bot rebuild a Lean file at its commit and read what every theorem in it depends on, under the admission rules every stranger's file is held to. Costs one credit, or two for a private check; buy credits and make an API key at https://qed.bot/check, and send it as Authorization: Bearer qed_.... Returns at once with the check queued; call get_check until it is done, which takes minutes. A file already checked in public is returned free, and a check that stops on qed.bot's side is refunded.

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": {
      "url": "<url>"
    },
    "name": "check_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesGitHub blob URL of the .lean file, at a full commit
privateNoOnly you can see the result (2 credits)
theoremNoThe theorem it proves, which must be declared

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give the safety profile (readOnly=false, idempotent, open-world). The description adds substantial context beyond them: credit cost, API-key auth via Bearer qed_..., where to obtain keys, asynchronous queueing semantics, free returns for already-checked public files, and refunds on server-side failure.

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?

Front-loaded with the core operation, then cost/auth, then async lifecycle and refund terms — good ordering. It is a dense, comma-chained paragraph that could be split, but nearly every clause carries operational weight.

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?

For an asynchronous, credit-metered, authenticated mutation tool with no output schema, it covers the full lifecycle: how to authenticate, what it costs, that it returns immediately, how to poll get_check, and what happens on free/refunded cases. Nothing needed to call it 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 coverage is 100%, so url, private, and theorem are already documented in the schema. The description adds meaning only for private by tying it to the 2-credit cost; it adds nothing for url format or the theorem declaration beyond what the schema states.

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?

States a concrete verb and resource: rebuild a Lean file at its commit and report theorem dependencies. The clause 'under the admission rules every stranger's file is held to' further characterizes the check, and naming get_check as the follow-up separates it from the polling sibling.

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?

Explicitly says to call get_check until the check is done, notes it takes minutes, and distinguishes the private (2-credit) variant from the public one. It also states the free-case and refund conditions, which directly shape when an agent should invoke it.

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