Skip to main content
Glama

Verify configured workspace

proof_verify_workspace

Runs verification artifacts defined in .proof-mcp.json, and checks candidate Lean/TLA+ artifacts without modifying the project when no manifest exists.

Instructions

Run artifacts from .proof-mcp.json. If no manifest exists, use proof_check_generated to check candidate artifacts without adding Lean or TLA+ files to the project.

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": "proof_verify_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 disclosure burden. It does convey a real behavioral dependency (a .proof-mcp.json manifest must exist) and implicitly hints at file side effects by noting the alternative avoids 'adding Lean or TLA+ files to the project'. It does not say what gets executed, whether project files are mutated, or what permissions are needed.

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?

Two short sentences, front-loaded with the primary action and immediately followed by the fallback condition. No filler, no restatement of the title.

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?

The tool is simple (no params, no nested objects) but also has no output schema and no annotations, so the description is the only source of truth about results and side effects. It never says what a successful or failed verification looks like, which matters for a verification entry point that an agent must interpret.

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 zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 applies; no parameter-level meaning is missing.

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 ('Run') and a specific resource ('artifacts from .proof-mcp.json'), and differentiates itself from proof_check_generated in the no-manifest case. It stops short of 5 because 'artifacts' is never concretized (Lean/TLA+ checks? generated files?) and the reader has to infer what 'running' them means.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit conditional routing rule: when no manifest exists, use proof_check_generated instead. That is a real when-not clause with a named alternative, but it only covers one branch and says nothing about when this tool is preferred over the other verification siblings present.

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