Skip to main content
Glama

Discover QA coverage

proof_discover_qa

Inspects workspace manifests and source extensions to report detected languages, modules, and candidate build/test commands, helping plan QA without executing project commands.

Instructions

Inspect workspace manifests and source extensions to report detected languages, modules, and candidate build/test commands. This is planning only and never executes project commands.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most important trait: this tool only inspects and never executes project commands, so it is safe to call speculatively. It does not state whether anything is written or cached, but the read-only contract is made explicit, which is the key behavioral fact here.

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 sentences, front-loaded with the action and its output, followed by the non-execution guarantee. No redundant restatement of the name or title and nothing that could be cut.

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 zero-parameter, no-annotation tool with no output schema, the description covers action, scope, and the return content well enough to invoke it correctly. The only gap is that it does not describe the report's shape or any limits on scanning (e.g., depth or ignored directories).

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 no parameter meaning to compensate for and the baseline applies. Nothing in the description conflicts with the empty input schema.

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

Purpose5/5

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

The description names a specific verb and resource ("inspect workspace manifests and source extensions") and states the exact report contents (languages, modules, candidate build/test commands). The closing clause "planning only and never executes project commands" cleanly separates it from the run/check siblings such as proof_run_python_test and proof_check_lean.

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?

The description implies the discovery/preparation phase by declaring it is planning-only, but it never says when to call it versus siblings like proof_verify_workspace or proof_prepare_verification, nor does it name any alternative. Usage is inferable but not stated.

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