Skip to main content
Glama

proof

Read-onlyIdempotent

Determine the verification scope for a single-file change by returning its change class, planned gates, and tools; run checks via CLI and keep command records and exit codes.

Instructions

Deterministic scope of a change to one file: its change class, planned gates and tools. Measured verification (--verify) runs gates and stays on the CLI. Successful structured results include the command record and exit code.

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": {
      "path": "<path>"
    },
    "name": "proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesExisting path, absolute or relative to the client directory.
taskNoa key of atlas.yaml/task_profilesdefault
changeNoa key of verification_policy/profilessource_change

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.63.0
    • changedInput schema / properties / path / description
      Previous value: -"the artifact the agent changed or is about to change"New value: +"Existing path, absolute or relative to the client directory."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, non-open-world operation. The description adds useful context beyond those annotations: it is deterministic, returns change class plus planned gates and tools, and structured results include a command record and exit code. It also clarifies that actual gate execution belongs to CLI `--verify`.

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?

The description is short and front-loads the core scope concept. The sentence about CLI `--verify` is useful but somewhat abrupt in an MCP tool description, and the first fragment is not a complete sentence, though neither causes serious ambiguity.

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?

With no output schema, the description must carry return-value information, and it does name the relevant outputs: change class, planned gates and tools, command record, and exit code. For a deterministic three-parameter scope tool, this is largely complete, though the notion of a 'command record' could be slightly clearer.

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 100%, with all three parameters documented in the input schema. The description does not add meaning about `path`, `task`, or `change` beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (a change to one file) and the intended outputs (change class, planned gates and tools), but the action verb is implicit rather than explicit. It does not name or contrast with any sibling tools such as gate or steps, so the agent must infer how this differs from them.

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?

It implies a boundary by noting that measured verification with `--verify` runs gates on the CLI, suggesting this tool is for deterministic scope preview rather than gate execution. However, there is no explicit when-to-use statement, no named alternative, and no guidance on when not to use the tool.

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