Skip to main content
Glama

task_update

Update a task's fields, progress note, or status. It automatically claims and renews the task, so no separate task_claim is needed; refuses if another operator holds it.

Instructions

Change a task: fields, a progress note, or status (done / deleted with reason / pending to reopen). Claims it for you first and renews your claim (never shortens it), so no task_claim is needed before or after an update; refuses if another operator holds it. Set waiting_on:"" to clear.

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": {
      "id": "<id>"
    },
    "name": "task_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id: the 8-character id shown in task_context/task_list (full UUID also works).
cwdNoSession folder (absolute path). Filled in by the OpenCode plugin; other clients pass the working folder.
dueNo
gateNoOperator methodology gate 0-8.
kindNo
noteNoDecision, evidence or verification. Not a command narration.
riskNoOperator methodology risk class.
tagsNosnake_case tags, one per item.
waitNoKeep out of NEXT until this date.
statusNodone only after the outcome is verified; owner-dependent work stays open with waiting_on.
dependsNoIds of tasks that must finish first. On update this replaces the list ([] clears it).
projectNo
priorityNo
repo_pathNoCanonical folder being changed. Defaults to the session folder (not operator lanes).
scheduledNo
waiting_onNoOwner-dependent: who must act (e.g. "owner approval"). Kept out of NEXT until cleared with "".
descriptionNo
remove_tagsNo
context_summaryNoHandoff-quality context: what, why, where it stands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses the non-obvious parts well: it auto-claims the task first, renews the claim without ever shortening it, and refuses when another operator holds it. Gaps remain around the destructive 'deleted' status — it implies a reason is captured but never says where, and never states whether deletion is reversible or what happens to dependents.

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?

Purpose is front-loaded, followed by claim semantics and then a parameter tip, all in three compact sentences with no filler. The middle clause is dense — a parenthetical and two semicolon-joined conditions — but every element carries information an agent needs.

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 19-parameter mutation tool with no annotations and no output schema, the description covers purpose, concurrency behavior, and status semantics but omits what the call returns on success or failure. Deletion consequences and how invalid field combinations are handled are also unaddressed, leaving meaningful gaps for a high-blast-radius update.

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 coverage is 63%, and the schema itself already documents status, waiting_on, depends, note, and id in comparable detail. The description adds operation-level meaning for status transitions (done / deleted with reason / pending to reopen) and the "" clearing convention for waiting_on, but says nothing about the other dozen-plus parameters (gate, risk, kind, remove_tags, wait, scheduled, repo_path, context_summary).

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

Purpose5/5

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

States a specific verb and resource ('Change a task') and enumerates the three modes of change: fields, a progress note, or a status transition. It distinguishes itself from task_claim by explicitly saying no task_claim is needed before or after, so an agent can separate it from the sibling without opening either schema.

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 clear when-to-use context (changing fields, notes, or status) plus an explicit alternative-avoidance rule for the most confusable sibling: task_claim is unnecessary, and the call refuses when another operator holds the task. It does not address when to prefer task_create or task_get over an update, but those boundaries are largely self-evident.

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