Skip to main content
Glama

conductor_verify_drift

Detect code drift by comparing static AST against spec invariants and a SHA-256 baseline lock, with optional strict mode to promote warnings to blocking errors.

Instructions

Run static AST drift detection against spec invariants and baseline lock.

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_verify_drift"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoRepository root path (defaults to cwd).
strictNoPromote warnings to blocking errors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It doesn't say whether the tool only reports drift or mutates anything, whether it exits non-zero or raises on drift, whether results are written to disk, or how 'strict' changes failure behavior beyond the terse schema note. 'Static AST' implies no execution, which is useful, but the failure/reporting model is left entirely undefined.

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?

A single front-loaded sentence with no filler; the verb and object lead. It is terse to the point that the jargon ('spec invariants', 'baseline lock') is unexplained, but nothing is wasted.

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?

There is no output schema and no annotations, so the description must explain what the tool returns and how failures manifest — and it does neither. For a verification gate that an agent may rely on to decide whether code is safe to ship, the missing return/failure semantics is 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 description coverage is 100%: both 'root' (defaults to cwd) and 'strict' (promote warnings to blocking errors) are documented in the schema. The description adds no extra meaning about what counts as drift or which invariants are checked. Baseline 3 is appropriate when the schema does all the parameter work.

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 states a specific verb and resource: 'Run static AST drift detection against spec invariants and baseline lock.' That is clearly distinct from siblings like conductor_lock_baseline (which presumably writes the baseline) and conductor_validate_spec (spec validation rather than drift). The jargon is dense but an agent can still tell it apart from the other conductor_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated prerequisites (e.g., that a baseline must be locked first), and no mention of when to prefer conductor_validate_spec instead. The 'baseline lock' phrasing hints that a lock is involved, but the agent must infer whether this tool requires one to already exist.

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