Skip to main content
Glama

Update task

update_task
Idempotent

Change one task: rename it, move it to another day, set or clear its time, or set or clear its reminder. Only pass the fields that change. Pass null for timeMinutes, reminderMinutesBefore or reminderAt to remove them. On a repeating occurrence this changes only that day (use update_repeating_task for the whole series). To change several tasks use update_tasks; to tick a task off use complete_task. Can be reverted with undo_last_change.

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
idYesTask id from get_week, list_tasks or search_tasks (also "repeat_…" ids of repeating occurrences).
titleNoNew title.
dayKeyNoMove to this day ("YYYY-MM-DD", "today" or "tomorrow"), or null to take the day away (Backlog).
reminderAtNo
timeMinutesNoNew start time in minutes after midnight, or null to make it an all-day task.
reminderMinutesBeforeNoReminder minutes before the start time, or null to turn the reminder off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-read-only behavior; the description adds real value on top by explaining that null removes a time/reminder, that edits on a repeating occurrence are scoped to that single day, and that the change is revertible via undo_last_change. It stops short of describing error behavior or what the response contains, which keeps it off a 5.

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?

Front-loaded with the primary action, then null semantics, then scope caveats, then sibling routing — four tight sentences with no filler. Slightly dense, but every clause carries an operational rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation with no output schema and strong annotations, this covers what an agent needs: partial-update semantics, null clearing, occurrence scoping, and alternatives. Reversibility is mentioned but not detailed (no undo scope or timing), a minor residual gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83% and the schema already documents each field, so the description mostly reinforces rather than introduces. The one genuine addition is the PATCH-style rule that only changed fields should be passed, plus the reminderAt-vs-reminderMinutesBefore distinction, which meaningfully reduces misuse.

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?

Names a specific verb and resource ("Change one task") and enumerates exactly what can change: rename, move day, set/clear time, set/clear reminder. It draws a clean boundary against the nearest siblings (update_repeating_task, update_tasks, complete_task), so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing rules: use update_repeating_task for a whole series, update_tasks for several tasks, complete_task to tick off. It also states the partial-update contract ("Only pass the fields that change") and the null-to-clear convention, which is the main way an agent misuses a PATCH-style tool.

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