Skip to main content
Glama

task_update

DestructiveIdempotent

Update task goals, constraints, or policy with an explicit reason while preserving the original request; budget changes require new user confirmation.

Instructions

Update goals, constraints or policy with an explicit reason; immutable original request is preserved. A preflight budget uses policy.preflight_core_hours plus preflight_budget_authorization containing the user's confirmation. Estimates are not authorization. A budget change requires a new confirmation; wall_seconds is the scheduler's reservation per job, not predicted usage.

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>",
      "changes": "<changes>",
      "reason": "<reason>",
      "op_id": "<op_id>"
    },
    "name": "task_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
reasonYes
changesYes
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?

Beyond the annotations, the description discloses important behavior: the original request is immutable, a reason is required, estimates are not authorization, budget changes need fresh confirmation, and wall_seconds is a scheduler reservation rather than predicted usage. It does not explicitly explain the destructive implications, but the annotations already flag destructiveHint=true.

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 description is dense but front-loaded, leading with the update purpose and then adding budget and confirmation semantics. Most sentences carry useful constraints, though the density and domain jargon could be clearer.

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?

For a destructive, idempotent update with five required parameters and nested changes, the description covers key behavioral safeguards but not the full parameter contract. The output schema can handle return values, but missing semantics for revision, op_id, token, and changes keeps it only partially complete.

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%, so the description must carry parameter meaning, but it only clarifies a few concepts such as reason, preflight budget authorization, and wall_seconds. Core parameters like task_id, revision, changes, op_id, and token remain unexplained, leaving substantial gaps for a six-parameter mutation tool.

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 clear verb and resource: update goals, constraints, or policy with an explicit reason. It is specific enough to distinguish updating from creating or reading, but it does not explicitly differentiate itself from nearby control or mutation siblings.

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?

Usage is implied for changing goals, constraints, policy, or budget details, and it adds that budget changes require a new confirmation. It does not state when to choose this tool over alternatives such as task_control, nor does it define exclusions.

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