Skip to main content
Glama

Run approved QA checks

proof_run_approved_checks

Executes only the QA command IDs a user explicitly approved, running local repository checks after the plan is reviewed. Use it to run selected approved checks.

Instructions

Execute only discovered command IDs that the user explicitly approved. This runs local repository code. Never call this tool until the user has seen the plan and approved the selected IDs.

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": {
      "approvedCommandIds": "<approvedCommandIds>"
    },
    "name": "proof_run_approved_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
approvedCommandIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 load, and it does disclose the two most important traits: this executes local repository code and requires explicit user approval beforehand. It does not cover execution sandbox/working directory, behavior on failure or timeout, or what an unapproved or unknown ID does.

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, no filler, and the safety-critical precondition is front-loaded in imperative form. Every clause carries a distinct constraint.

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?

For a single-parameter tool with no output schema and no annotations, the definition covers the approval gate and the code-execution risk but leaves out return shape and failure handling. Adequate to prevent the dangerous misuse, not complete enough to predict results.

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 adds real meaning by establishing provenance ('discovered' IDs) and an approval requirement for the values, but says nothing about the array's cardinality (1-30) or the required 'qa-' identifier format, which only the schema conveys.

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 and resource: 'Execute only discovered command IDs that the user explicitly approved.' The word 'only' plus 'discovered' implicitly separates it from the discovery step (proof_discover_qa), but no sibling is named, so differentiation relies on inference.

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 hard precondition: 'Never call this tool until the user has seen the plan and approved the selected IDs.' That is a clear when-not rule, but it never explicitly names the tool to call first to obtain the IDs, nor does it describe what to do if no IDs have been discovered.

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