Skip to main content
Glama

Model check TLA+

proof_check_tla

Run TLC model checking on a workspace-relative TLA+ module and configuration to detect specification errors and validate model behavior.

Instructions

Run TLC on a workspace-relative TLA+ module and TLC configuration.

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": {
      "specPath": "<specPath>",
      "configPath": "<configPath>"
    },
    "name": "proof_check_tla"
  }
}

Input Schema

NameRequiredDescriptionDefault
specPathYes
configPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that paths are workspace-relative, but does not state whether the operation is long-running, what it returns, whether it mutates state, or what permissions or prepared workspace state are required.

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?

The description is a single efficient sentence with no wasted wording and the key constraint (workspace-relative) is front-loaded. It is appropriately sized for a tool whose structured fields are otherwise sparse.

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

Completeness2/5

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

With no annotations, no output schema, and 0% schema description coverage, the description is too thin for a model-checking tool. An agent cannot tell how long TLC may run, what constitutes success or failure, or whether any setup must precede the call.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It does add meaning by identifying specPath as a workspace-relative TLA+ module and configPath as a TLC configuration, but it gives no format, extension, or example details beyond those labels.

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 states a specific verb (Run TLC) and resource (a workspace-relative TLA+ module and TLC configuration), which clearly distinguishes it from siblings like proof_check_lean. It is clear what the tool does, though it does not explicitly name alternative tools for non-TLA+ verification.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The TLA+ context implies usage, but the agent receives no routing logic for choosing between this and sibling proof-checking tools.

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