Skip to main content
Glama

Update Task

update_task

Modify a task's status, priority, title, or description by ID to keep project records current and workflow state accurate.

Instructions

Update a task's status, priority, or description by ID.

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": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
titleNoNew title (if changing).
statusNoOne of: pending, in_progress, blocked, completed, cancelled.
task_idYesThe task ID (e.g. TASK-0001).
priorityNoOne of: critical, high, medium, low.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool, yet it discloses nothing about permissions, whether changes are reversible, or what the return looks like. The most consequential unknown is undisclosed: every field has a default of empty string, so it is unclear whether omitting a field leaves it unchanged or clears it, which directly affects how an agent should call the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is appropriately short and front-loads the verb and resource, with no padding. But its brevity is achieved by listing fields inaccurately rather than by precise compression, so the concision costs correctness.

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?

For a mutation tool with zero annotation coverage, five parameters, and partial-update semantics implied by empty-string defaults, the description is too thin. It does not need to explain return values because an output schema exists, but it should clarify partial-update behavior and its relationship to complete_task, and it should not contradict the parameter set.

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 coverage is 100%, so the input schema already documents all five parameters including the enum-like value lists for status and priority, and the description adds no meaning beyond that. Worse, it actively misleads by naming a 'description' field that does not exist and silently dropping 'title' and 'path', so an agent following the description would construct a wrong call.

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 and resource ('Update a task's ... by ID') and enumerates the updatable fields, so the core purpose is identifiable. However, the enumerated fields do not match the schema: it lists 'description', which is not a parameter, and omits 'title' and 'path', which are. That mismatch blunts what is otherwise a clear statement of purpose and leaves it undifferentiated from the sibling complete_task.

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 guidance on when to use this tool instead of the closely related siblings create_task, complete_task, or add_task. An agent must infer from the name alone whether to call complete_task or update_task with status=completed, and no prerequisites or exclusions are stated.

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