Skip to main content
Glama

update_task

Change a task: priority, duration, deadline (null removes it), earliest start, block sizes, notes, whether it gets planned (autoSchedule), work or personal (hoursType), or status (done when finished: its upcoming blocks stay in the calendar as done and it stays in the list as done; archived to drop it; open to reopen).

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

Input Schema

NameRequiredDescriptionDefault
idYes
notesNo
titleNo
statusNo
deadlineNoDue by; a bare date means end of day
priorityNo1 = niedrig, 2 = normal, 3 = hoch, 4 = kritisch
hoursTypeNoWhere the planner puts it: "work" (default) inside working hours, "personal" for private things planned outside working hours, in the user's personal time (evenings, weekends)
autoScheduleNoWhether the planner puts the task in the calendar. Tasks imported from Jira or GitHub start with false until the user picks them; set true to plan one, false to keep it on the list without planning it
earliestStartNoNot before
durationMinutesNoTotal time the task needs
maxBlockMinutesNoThis task's own cap on one block. Don't set block limits if not specifically asked. Without it the task follows the user's setting (no cap unless they set one); null removes the task's own cap
minBlockMinutesNoShortest block worth planning. Don't set block limits if not specifically asked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnly=false and destructive=false, so the description carries most of the burden and delivers real side-effect detail: setting status=done leaves upcoming blocks in the calendar as done and keeps the task in the list, archived drops it from the list, open reopens it, and null on deadline removes it. What is missing is what happens to unspecified fields and whether a failed/unknown id errors out. Nothing here contradicts the annotations.

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 that names the resource first and then the mutable fields, with no filler. The nested parenthetical for status is dense and slightly hard to parse, but every clause 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 12-parameter mutation tool with no output schema, the description covers the behaviorally tricky fields well but leaves gaps: durationMinutes and title are never referenced, and there is no statement about the result of the call or about partial-update semantics. Adequate to call the tool correctly for most edits, but not complete.

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?

With 12 parameters at 67% schema coverage, the schema already documents priority, hoursType, autoSchedule, block caps and the date-time format. The description adds genuinely useful meaning for two of them — "deadline (null removes it)" and the status lifecycle — but merely restates the rest as a field list. It also never mentions durationMinutes or title, so it does not fully compensate for the uncovered parameters.

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?

Opens with a specific verb+resource ("Change a task") and then enumerates virtually every mutable field: priority, duration, deadline, earliest start, block sizes, notes, autoSchedule, hoursType, status. That is enough for an agent to distinguish it from create_task or delete_task without opening the schema. It stops short of naming a sibling for differentiation, which keeps it at 4 rather than 5.

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 by the field enumeration and by the status-value semantics (done/archived/open), so an agent can infer that this is the tool for modifying an existing task. There is no explicit "use create_task to add a task" or "use delete_task to remove it permanently" routing, and no stated preconditions such as needing a valid task id.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources