Skip to main content
Glama

Prepare source verification

proof_prepare_verification

Discovers source files in an optional scope, gathers bounded source context and a Clarity dependency graph, then returns instructions for drafting properties and candidate Lean/TLA+ verification artifacts.

Instructions

Discover source files in an optional scope, collect a bounded source context and Clarity dependency graph, and return instructions for the agent to draft properties and candidate Lean/TLA+ artifacts.

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

Input Schema

NameRequiredDescriptionDefault
purposeNo
maxFilesNo
scopePathsNo
maxCharactersNo
includeClarityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose that context collection is bounded and that a dependency graph is collected. It does not state that the operation is read-only/non-destructive, what happens when scopePaths is empty (whole workspace?), what permission or size failure modes exist, or that no verification is performed here. Those omissions matter for a 5-parameter tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with three parallel verbs and no filler; every clause adds information. The compressed noun stacking ('bounded source context and Clarity dependency graph') costs a little readability but nothing is wasted.

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?

Five parameters, no annotations, no output schema, and no parameter documentation, so the description is the only source of behavioral detail. It covers the overall flow and the shape of the return (agent instructions) but omits the purpose input and any limits or failure behavior, leaving real gaps for a prep tool.

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%, so the description must compensate, and it largely does not. It hints at scopePaths ('optional scope'), maxFiles/maxCharacters ('bounded') and includeClarity ('Clarity dependency graph'), but never mentions the purpose parameter at all, and gives no defaults or limits for the bounds. The mapping is allusive rather than explanatory.

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 names three concrete actions (discover source files, collect bounded context plus Clarity dependency graph, return drafting instructions) and the artifact types (properties, Lean/TLA+ candidates). That is a specific verb+resource statement with a clear pipeline shape that distinguishes it from the proof_check_* siblings, which presumably act on already-drafted artifacts. It stops just short of a crisp one-line summary of its role in the workflow.

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

Usage Guidelines3/5

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

Usage is only implied: returning 'instructions for the agent to draft properties' suggests this is the first step before the check tools, but no explicit when-to-use, when-not-to-use, or named alternative is given. An agent must infer sequencing from the sibling names and the drafting framing. Adequate but not decision-ready.

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