Skip to main content
Glama

lean_verify

Run sandboxed Lake proof verification against an approved package's default targets to confirm proofs compile offline and report failed, unavailable, or invalid-input outcomes.

Instructions

Run sandboxed Lake proof verification on the approved package's default targets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lean_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two meaningful traits: execution is sandboxed and scope is limited to the package's default targets rather than arbitrary files. However, it says nothing about expected runtime, whether failures raise errors or return results, side effects on build artifacts, or what a successful run yields, which matters for a verification-time tool with zero annotation coverage.

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?

A single front-loaded sentence with no filler; the essential noun phrase ('sandboxed Lake proof verification') leads and the scope qualifier follows.

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?

For a zero-parameter tool the input side is complete, but with no annotations and no output schema the description is the only source of information about results. It does not say what verification returns on success or failure, or how it relates to lean_diagnostics, leaving the agent without enough context to interpret the outcome.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the schema to describe and no semantics to compensate for; the baseline of 4 applies. The phrase 'default targets' helpfully signals that target selection is fixed rather than caller-configurable.

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?

States a specific verb+resource: 'Run sandboxed Lake proof verification' on 'the approved package's default targets.' It is clear what the tool does, though it never distinguishes itself from the sibling lean_diagnostics, and 'approved package' is left undefined (which package, approved how).

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?

No when-to-use guidance is given. It never says when to reach for verification versus lean_diagnostics, whether a build must happen first, or what the preconditions ('approved package') are. The agent must infer all of this.

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