Skip to main content
Glama
RocqSolid
by bn-peters

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROCQ_LSP_BINARYNoThe `coq-lsp` executable (default `coq-lsp`)
ROCQ_LSP_TIMEOUTNoDeadline per call; set slightly below the MCP tool timeout (default `55`, max `3600`)
ROCQ_LSP_USE_OPAMNoRun via `opam exec --`; `0` runs the binary directly (default `1`)
ROCQ_LSP_WORKSPACENoOverride the inferred workspace root (default unset)
ROCQ_LSP_DUNE_BUILDNoBuild dune dependencies before checks; `0` disables (default `1`)
ROCQ_LSP_MAX_ERRORSNoMax errors `coq-lsp` collects (default `1000000`)
ROCQ_LSP_DUNE_TIMEOUTNoLimit per dune detection or build command (default `55`, max `3600`)
ROCQ_LSP_MESSAGE_LIMITNoMax errors returned per check (default `10`, max `50`)
ROCQ_LSP_COMMAND_TIMEOUTNoDefault per-sentence timeout; `0` disables (default `5`)
ROCQ_LSP_IDLE_TTL_SECONDSNoIdle time before cached sessions are stopped (default `1800`)
ROCQ_LSP_HARD_TIMEOUT_GRACENoExtra wait after cancellation before the session is killed (default `5`)
ROCQ_LSP_TIMEOUT_AFTER_ERRORNoOverall deadline for the rest of a check after its first error; `0` disables (default `10`)

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
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
rocq_check_fileA

Check a Rocq file and report diagnostics.

Use this to check files for errors. (To find warnings, recompile the file manually.) Error diagnostics include the source sentence and the proof state at error positions.

The first error in a file is always reported, along with later errors reached within the after-error deadline. The list of errors may be truncated. The tool also reports Rocq sentences running for long time.

This tool is efficient due to per-file caching. For dune-based Rocq projects, it attempts to rebuild dependencies before checking and restarts the cached coq-lsp process when that applies. Use clear_cache = true when project files have changed or dependencies were rebuilt outside dune.

Timeouts are handled gracefully, and partial diagnostics are returned when possible. Repeated checks after timeouts use the cache.

rocq_run_atA

Run Rocq commands at a file position and return their output.

Use this for running Rocq commands, such as:

  • Search Nat.add.

  • Search insert delete "_eq".

  • Check (3 + 4).

  • About Nat.add.

  • Locate "+".

  • Show. (to show the proof state at a position) The tool is also useful for one-off debugging tasks.

Prefer calling this tool right after imports or between lemmas/definitions. Only use within proofs when necessary.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation4/5

The two tools have distinct primary purposes: file-level diagnostics versus running Rocq commands at a specific position. There is minor overlap around proof-state inspection, but the descriptions make the intended use clear.

Naming Consistency4/5

Both names use the same `rocq_` prefix and snake_case, which is predictable. The action phrasing is slightly inconsistent (`check_file` versus `run_at`), but still readable and coherent.

Tool Count3/5

Two tools is thin for a Rocq interaction server, even though both are broad and useful. The surface relies heavily on `rocq_run_at` for many query and debugging tasks.

Completeness4/5

The pair covers file checking and arbitrary Rocq command execution, which enables most core workflows. Minor gaps remain, such as warning retrieval requiring manual recompilation and no dedicated proof-state/inspection tool beyond using `rocq_run_at`.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues