Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LEAN_PLUGIN_PROJECTYesAbsolute path to the approved Lake workspace root.
LEAN_PLUGIN_TOOLCHAINYesAbsolute path to the unpacked Lean Linux release directory.
LEAN_PLUGIN_LAKE_CHECK_TIMEOUT_SECONDSNoOptional timeout for the lake check phase, in whole seconds from 240 to 600. An invalid setting prevents the server from starting.240

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
lean_diagnosticsC

Elaborate a project-relative Lean source file in the approved Lake workspace.

lean_verifyB

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: lean_diagnostics elaborates a specific source file, while lean_verify runs package-level proof verification. An agent can easily choose between them based on whether it needs file diagnostics or target verification.

Naming Consistency4/5

Both tools use the same lean_ prefix and snake_case style, which is predictable. The only minor inconsistency is grammatical form: diagnostics is a noun while verify is a verb, but the pattern remains readable.

Tool Count3/5

Two tools is thin for a Lean plugin, even a narrowly scoped one. It covers the two core operations but leaves little room for related workflows, making the count borderline.

Completeness3/5

The surface covers file elaboration and package verification, but notable gaps remain: no build/clean, no listing or reading files, and no way to verify a specific non-default target. Agents may be able to work around some of these, but the lifecycle is incomplete.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues