Skip to main content
Glama

task_update

Update task status, attach handoff notes, and record branch or PR metadata so sequential or concurrent chats stay aligned on project work.

Instructions

Advance task status (TODO, IN_PROGRESS, BLOCKED, IN_REVIEW, DONE, CANCELLED), attach concise handoff_notes for downstream chats, or record optional branch/PR metadata.

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

Input Schema

NameRequiredDescriptionDefault
briefNo
filesNo
titleNo
pr_urlNo
statusNo
task_idYesTask slug ID to update.
project_idNoOptional project ID (auto-resolved when omitted).
branch_nameNo
target_testsNo
handoff_notesNoConcise Markdown summary for downstream chats.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether omitted fields are left untouched or cleared, whether status transitions are validated, whether the update is idempotent, or what permissions are required. For a 10-parameter mutation tool, that is a substantial disclosure gap.

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?

A single front-loaded sentence with parallel clauses and zero filler. It is dense but structurally sound; it could be tightened slightly given how much it omits, but there is no wasted wording.

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?

With 10 parameters, no annotations, no output schema, and low schema coverage, the description should explain partial-update semantics and the undescribed fields. It omits both, so an agent knows the rough purpose but not enough to call the tool confidently or correctly.

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 only 30% across 10 parameters, so the description must compensate, but it only gestures at status, handoff_notes, branch_name and pr_url — and the status enum and handoff_notes meaning are already in the schema. The remaining parameters (brief, files, title, target_tests) receive no explanation of format or intended content.

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+resource ('Advance task status') and enumerates the full status vocabulary plus the two other updateable concerns (handoff_notes, branch/PR metadata). It is clear what the tool does, but it never differentiates itself from close siblings like ui_update_task or task_start, so an agent cannot disambiguate from the definition alone.

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 when-to-use or when-not-to-use guidance, and no named alternative. The only contextual hint is that handoff_notes are 'for downstream chats', which implies a handoff workflow but does not tell the agent when this tool should be chosen over ui_update_task or task_start.

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