Skip to main content
Glama

validate_feature_protocols

Validates a feature against active protocols before starting a worker, returning whether it can proceed and any constraint violations.

Instructions

Validate a feature against all active protocols before starting a worker. Returns whether the feature can proceed and any constraint violations.

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

Input Schema

NameRequiredDescriptionDefault
featureIdYesID of the feature to validate
projectDirYesAbsolute path to the project directory
customPromptNoOptional custom prompt to include in validation context

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 disclosure burden. It usefully reveals the return semantics (proceed/violations) and implies a non-mutating check, but says nothing about prerequisites (must active protocols exist first?), whether it records violations that get_violations would later surface, or whether a failed validation blocks enqueue/worker start.

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?

Two sentences, zero filler, and the operational trigger is front-loaded before the return-value note. Nothing in the text is redundant with the title or restates the name.

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?

There is no output schema and no annotations, so the description must compensate; it partially does by summarizing the response (can proceed plus constraint violations). However, for a validation gate that sits before worker startup, the absence of prerequisite and blocking-behavior details leaves a meaningful 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% with all three parameters documented, so the schema already does the heavy lifting. The description adds only the implicit note that all active protocols are checked (no protocol-selection parameter) and nothing about how customPrompt affects the validation context.

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 (validate a feature against all active protocols) plus the lifecycle moment ('before starting a worker'), which distinguishes it from validate_workers. It does not explicitly name any sibling as the alternative, but the operation and its scope are unambiguous.

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 trigger condition: call this before starting a worker. There are no stated exclusions or named alternatives (e.g., when to use validate_workers or check_worker instead), so it stops short of full routing guidance, but the when-to-use context is concrete.

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