Skip to main content
Glama

configure_verification

Set pre-completion verification commands workers must run before marking a feature complete, enforcing type checks, linting, or tests and fixing errors first.

Instructions

Configure pre-completion verification commands that workers must run before marking a feature as complete. Use this to enforce type checking, linting, or tests.

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>"
    },
    "name": "configure_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoClear all verification commands (default: false)
commandsNoCommands workers must run before completion (e.g., ['npm run build', 'npx tsc --noEmit'])
projectDirYesAbsolute path to the project directory
failOnErrorNoWhether workers should fix errors before proceeding (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the most important behavior: the configured commands become mandatory gates that workers must run before marking completion. It leaves out what happens to pre-existing commands (replace vs merge), whether configuration persists across sessions, and what failure looks like when a worker's command exits non-zero.

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, tightly written, with the core action and enforcement point front-loaded. The second sentence is somewhat redundant with the first's "verification commands" but earns its place by giving concrete example categories.

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 four-parameter configuration tool with full schema coverage and no output schema, the description covers the essential what and why. The main residual gap is merge/overwrite semantics for the commands array, which the schema does not address either.

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 every parameter including clear and failOnError is already documented in the schema, establishing a baseline of 3. The description's mention of type checking, linting and tests loosely maps to the commands array but adds no format, ordering, or interaction detail beyond the schema.

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 pairs a specific verb ("Configure") with a specific resource ("pre-completion verification commands") and states the enforcement point (before marking a feature complete). It does not name the closely related sibling run_verification, so the agent must infer the configure-vs-execute split from the verbs alone.

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?

"Use this to enforce type checking, linting, or tests" gives concrete usage contexts, which is better than nothing. However there is no guidance on when not to use it, no mention of run_verification as the alternative for actually executing checks, and no note on prerequisites such as the project needing an existing build setup.

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