Skip to main content
Glama

task_background

DestructiveIdempotent

Enable or hold future automatic Codex continuations for one project without interrupting current work or active jobs; pending decisions remain saved.

Instructions

Enable or hold future automatic Codex continuations for one project. Running continuations finish their current turn; this does not cancel them or active analyses/jobs. Read active_background before taking over. To interrupt immediately use task_control pause and read current work before resuming. Pending decisions remain saved. Shared setup and other projects stay unchanged.

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>",
      "enabled": "<enabled>",
      "op_id": "<op_id>"
    },
    "name": "task_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
enabledYes
task_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds real context beyond them: running continuations finish their current turn, active analyses/jobs are not cancelled, pending decisions stay saved, and other projects and shared setup are untouched. That is exactly the 'what changes and what survives' information an agent needs before a destructive call. It does not explain why a hold is considered destructive or what permissions 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?

The lead sentence is front-loaded with purpose and the remaining sentences are short and scoped to distinct facts. There is mild redundancy between 'Read active_background before taking over' and 'read current work before resuming,' but no filler sentences.

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?

An output schema exists, so return values need no explanation, but the definition leaves the agent unequipped on the input side: five undocumented parameters including revision and op_id with no hint of their semantics or ordering constraints. For a destructive, idempotent-flagged operation, that is a substantial omission despite the good behavioral narrative.

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?

Schema description coverage is 0% across five parameters, so the description carries the full burden and largely fails it. Only 'one project' loosely maps to task_id and 'enable or hold' loosely maps to enabled; revision, op_id, and token — the concurrency and idempotency controls — get no mention at all, which is a serious gap for a destructive mutation.

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 names a specific verb pair and object: 'Enable or hold future automatic Codex continuations for one project.' That is far more specific than the name alone, and it distinguishes the tool's scope ('future' continuations) from immediate intervention. It stops short of a crisp one-line framing that would let an agent separate it from siblings like background_request without extra reading.

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?

It gives a concrete prerequisite ('Read active_background before taking over') and an explicit alternative for the contrasting case ('To interrupt immediately use task_control pause'). What is missing is the inverse case: when a pending continuation should simply be left alone rather than enabled or held.

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