Skip to main content
Glama

validate_workers

Validates feature readiness, dependency chains, and potential conflicts before launching parallel workers, so issues are caught before execution.

Instructions

Pre-flight validation before starting parallel workers. Checks feature readiness, dependency chains, and potential conflicts.

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

Input Schema

NameRequiredDescriptionDefault
featureIdsYesArray of feature IDs to validate for parallel execution
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 load. It discloses the three things checked, but not whether validation is read-only or mutates state, whether a failure blocks execution, or what the result contains.

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 tight sentences with the pre-flight purpose front-loaded and the check list following. No filler, though it ends before telling the agent anything actionable about the result.

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?

With no output schema, the description should convey whether it returns a pass/fail, a conflict list, or remediation guidance. For a gating validation step that omission leaves a real gap.

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 coverage is 100% and both parameters are documented in the schema, so baseline is 3. The description adds only that featureIds are validated "for parallel execution," not per-parameter meaning 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?

States a specific verb and object ("Pre-flight validation") plus concrete check targets: feature readiness, dependency chains, conflicts. An agent can distinguish it from start_parallel_workers or check_rollback_conflicts, though it does not explicitly name those siblings.

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 clear timing condition: use before starting parallel workers. It does not state when to skip it, whether it is mandatory prior to orchestration, or which sibling performs the actual start.

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