Skip to main content
Glama

validation_control

DestructiveIdempotent

Suspend reuse of an invalid plan and its pending batches while retaining running evidence and costs; corrected settings create a new plan using reuse_from for still-valid components.

Instructions

Suspend reuse of an invalid plan and its pending batches, retaining running evidence and costs. Corrected settings get a new plan with reuse_from for still valid components.

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": {
      "task_id": "<task_id>",
      "revision": "<revision>",
      "plan_id": "<plan_id>",
      "reason": "<reason>",
      "op_id": "<op_id>"
    },
    "name": "validation_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
reasonYes
plan_idYes
task_idYes
revisionYes
componentsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the safety profile is known. The description adds real value beyond that by disclosing that running evidence and costs are retained, pending batches are suspended, and valid components survive for reuse. It still does not say whether the suspension is reversible or what permissions/state are required.

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 dense sentences with the primary effect front-loaded and no filler. The wording is jargon-heavy and leans on an undefined 'reuse_from' field, which slightly reduces clarity.

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?

Output schema exists, so return values need not be described. But for a destructive, multi-parameter mutation, the description omits parameter meanings, preconditions, and the reversibility of the suspension, leaving the agent without enough to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 7 parameters (task_id, revision, plan_id, reason, op_id, token, components), and the description explains none of them. It references a 'reuse_from' concept that is not even a parameter, while the five required identifiers and the optional components list go undefined in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (an invalid plan and its pending batches) and the effect (suspending reuse while retaining evidence and costs), which is more specific than the generic name 'validation_control'. However, it never states the operative verb unambiguously (invalidate? suspend? cancel?) and gives no differentiation from siblings such as validation_plan, validation_check, or batch_control.

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 explicit statement of when to call this versus validation_check or validation_plan. The second sentence implies a follow-up workflow ('Corrected settings get a new plan with reuse_from'), but that describes what happens after, not the condition that selects this tool.

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