Skip to main content
Glama

conductor_validate_spec

Validates conductor.spec.yaml schema and invariants before AI coding execution, catching spec errors early so agents start from a compliant, verifiable baseline.

Instructions

Validate conductor.spec.yaml schema and invariants before AI coding execution.

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": "conductor_validate_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoRepository root path (defaults to cwd).
spec_pathNoOptional spec path relative to root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full disclosure burden, and it does not say whether the tool is read-only, what happens when validation fails (thrown error vs. returned findings), or whether any state is written. The word "validate" weakly implies a non-mutating check, but that is inference, not disclosure.

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?

A single eleven-word sentence with the verb first and the qualifying timing clause last; nothing is padding and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a pre-execution gate tool with zero annotations and no output schema, the agent is left without the information that matters most: what a failure looks like and how to react to it, and what class of invariants is checked. Adequate to identify the tool's target, inadequate to invoke and interpret it confidently.

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% for both parameters (root defaults to cwd, spec_path is optional relative to root), so the schema already does the work. The description adds only the implied default filename conductor.spec.yaml, which is a marginal supplement rather than a real semantic expansion.

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?

Names a specific verb (validate) against a specific artifact (conductor.spec.yaml, covering both schema and invariants), plus the lifecycle point where it applies. It is distinguishable from the checkpoint/lock/rollback siblings, though it does not explicitly contrast with conductor_verify_drift, which arguably also checks something.

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?

"before AI coding execution" gives an implied timing trigger, which is real guidance. There is no explicit when-not condition, no statement about whether it must be run once per change or can be rerun freely, and no named alternative for the drift-check sibling.

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