Skip to main content
Glama

Check Lean proof

proof_check_lean

Validates a workspace-relative Lean 4 file, treating warnings as errors to catch issues before theorem proofs are accepted.

Instructions

Check one workspace-relative Lean 4 file with warnings treated as errors.

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": {
      "filePath": "<filePath>"
    },
    "name": "proof_check_lean"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 usefully discloses the strictness policy ('warnings treated as errors') and the workspace-relative path requirement, but says nothing about whether the check is read-only, whether it modifies build artifacts, how long it may run, or what a failure result looks like.

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?

One front-loaded sentence containing the action, the target, and the strictness modifier. Nothing is redundant and nothing needed to be reordered.

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 one-parameter tool with no annotations and no output schema, the description should convey what the agent gets back or how failures surface. It covers the strictness and path semantics but leaves the result shape and error behavior unexplained.

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?

Schema coverage is 0% and the schema only declares a non-empty string, so 'workspace-relative' is the key semantic constraint that determines passing vs. failing an absolute path. Some residual ambiguity remains (file extension expectations, whether subdirectories are allowed), which keeps it below a 5.

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?

The description gives a specific verb ('Check') and resource ('one workspace-relative Lean 4 file'), and the 'Lean 4' qualifier separates it from language-specific siblings like proof_check_tla. It does not explicitly contrast with proof_check_generated or proof_verify_workspace, but the single-file Lean scope is unambiguous.

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?

Usage is only implied: 'one ... file' signals single-file granularity vs. a whole-workspace check, and 'workspace-relative' constrains what paths are valid. There is no explicit when-to-use vs. when-not guidance and no named alternative for batch or workspace-wide verification.

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