Skip to main content
Glama

task_control

DestructiveIdempotent

Pause, resume, or stop simulation jobs, cancel queued file-producing work, and keep active remote jobs and diagnostics accessible.

Instructions

Pause future dispatch and queued file-producing work, resume, or stop and cancel active jobs. Persists intent first. Existing remote jobs keep running on pause; log reads, collection and diagnostic checks remain available.

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>",
      "action": "<action>",
      "op_id": "<op_id>"
    },
    "name": "task_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
actionYes
task_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds genuinely new behavior: intent is persisted first, remote jobs survive a pause, and read/collection/diagnostic paths stay usable. This is meaningful operational context beyond the annotation flags. It stops short of covering permission requirements or what the concurrent-write failure mode looks like for a destructive action.

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?

Three short sentences, front-loaded with the core verb set and then the behavioral caveats. No filler or restatement of the title. A bulleted action list would have been marginally clearer, but the prose is dense and earns its space.

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?

The output schema means return values need no explanation, and the behavioral narrative is solid for a destructive control tool. The gap is that three of four required inputs remain undefined in both schema and description, leaving an agent unable to construct a correct call from the definition alone.

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

Parameters2/5

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

All four required parameters have 0% schema description coverage, so the description carries the full burden and largely drops it. It implies the values the 'action' parameter accepts (pause/resume/stop) but never enumerates or names that parameter, and 'revision' and 'op_id' — critical for a destructive, idempotent operation — are never explained at all.

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 specific operations on a specific resource: pause future dispatch and queued file-producing work, resume, or stop and cancel active jobs. An agent can tell this is a lifecycle-control tool rather than a read or update tool. It does not name which sibling (e.g. task_update or task_release) handles overlapping cases, so differentiation is only partial.

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?

The clause 'Existing remote jobs keep running on pause' gives real semantic guidance for choosing pause over stop, and 'log reads, collection and diagnostic checks remain available' clarifies what this tool does not block. However, there is no explicit routing to alternatives such as task_update, task_release or batch_control, so the agent must infer when this tool is the wrong choice.

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