Skip to main content
Glama

Check generated formal artifacts

proof_check_generated

Checks agent-drafted Lean and TLA+ content without requiring repository files, optionally saving the checked bundle, properties, and assumptions under .proof-mcp/generated/.

Instructions

Check agent-drafted Lean and/or TLA+ content without requiring formal files in the repository. Optionally retain the checked bundle and its properties/assumptions under .proof-mcp/generated/.

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_check_generated"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNo
tlaConfigNo
tlaSourceNo
leanSourceNo
propertiesNo
assumptionsNo
sourceFilesNo
observationsNo
persistGeneratedNo

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 one behavioral trait - optional retention of the checked bundle plus its properties/assumptions under .proof-mcp/generated/ - which tells the agent this tool can write to disk. It says nothing about whether external provers are invoked, expected latency, failure semantics, or what 'check' actually validates.

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 compact sentences, zero filler, with the core capability front-loaded and the optional side effect placed second. Every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no annotations and no output schema, the definition is too thin: the agent cannot tell what a successful check returns, what distinguishes sourceFiles from inline sources, or what 'observations' are for. The persistence detail helps, but the definition is not sufficient on its own.

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

Parameters2/5

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

Schema description coverage is 0% across 9 parameters, so the description must compensate. It loosely maps about half of them (leanSource/tlaSource, properties, assumptions, persistGenerated) but leaves 'purpose', 'tlaConfig', 'sourceFiles', and 'observations' with no explanation, and gives no format or semantic detail for what a 'property' or 'assumption' string should contain.

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 ('Check') and resource ('agent-drafted Lean and/or TLA+ content') and scopes it with 'without requiring formal files in the repository', which implicitly separates it from the file-based siblings proof_check_lean and proof_check_tla. It does not name those siblings explicitly, so differentiation is inferred rather than declared.

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 a clear use condition: content that is agent-drafted and not present as repository files. There are no explicit exclusions or named alternatives telling the agent when to prefer proof_check_lean/proof_check_tla instead, so it falls short of a full when/when-not treatment.

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