Skip to main content
Glama

run_verification

Runs safe verification commands like npm test, pytest, or cargo test in a project directory to check whether a feature works correctly.

Instructions

Run a verification command (e.g., tests, linting, build) to check if a feature works correctly. Only allows safe commands like npm test, pytest, cargo test, etc.

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": {
      "projectDir": "<projectDir>",
      "command": "<command>"
    },
    "name": "run_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesThe command to run for verification (e.g., 'npm test', 'pytest', 'cargo test')
featureIdNoOptional feature ID this verification is for
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 burden. It does disclose one real behavioral trait — an allowlist gate restricting commands to "safe" ones — which is valuable context an agent cannot get elsewhere. However, it never defines what makes a command 'safe', what happens when a command is rejected, whether failures are surfaced as errors, how long-running commands time out, or whether running tests may write files.

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?

Two sentences, front-loaded with the action and immediately followed by the constraint — efficient and easy to scan. Minor waste in the trailing "etc." and the slightly vague "safe commands" phrasing, which weakens precision without adding length.

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?

The tool is simple (3 params, flat schema, full coverage), so much is covered. But there is no output schema, which means the description should say what a verification run returns — pass/fail, exit code, captured stdout/stderr, or a summary — and it says nothing, leaving the agent unable to anticipate the result shape. Failure and rejection semantics are also absent.

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%, so all three parameters (command, projectDir, featureId) are already documented in the schema, setting the baseline at 3. The description's command examples ('npm test', 'pytest', 'cargo test') add illustrative value and the safe-command restriction adds a semantic constraint, but neither required-parameter (absolute path for projectDir) nor featureId linkage is clarified further.

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 ("Run a verification command") and enumerates the domain of commands (tests, linting, build). It is distinguishable from configure_verification by the verb 'run', but it never names or contrasts a sibling, so it stops short of full differentiation.

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 — the agent must infer this is used after implementing a feature "to check if a feature works correctly." There is a constraint ("Only allows safe commands") but no explicit when-to-use versus alternatives such as run_review or configure_verification, and no stated prerequisites like needing a projectDir with a configured setup.

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