Skip to main content
Glama

Update a task

update_task
DestructiveIdempotent

Change a task's fields. Only the fields you pass change; their previous values are overwritten.

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
dowNoDays of the week as a bitmask: Monday=1, Tuesday=2, Wednesday=4, Thursday=8, Friday=16, Saturday=32, Sunday=64. 127 = every day, 31 = weekdays. 0 = none (use with cron or every_days).
cronNoCron schedule, 5 fields; only the date fields (day of month, month, weekday) matter: minute and hour are ignored, so write them as "0 0" (e.g. "0 0 * * 1" = Mondays). Alternative to dow and every_days (one schedule system at a time). Do not use "*/N" in the day field for "every N days": it restarts each month; use every_days.
nameNoTask name.
everyNoSubtasks: armed every N runs of the parent.
task_idYesThe task's id (from list_tasks, todays_tasks or a loop's tasks).
end_dateNoLast day it applies, YYYY-MM-DD. null clears it.
is_activeNofalse pauses it without deleting it.
task_typeNo"schedule": due on its dow, cron or every_days days (exactly one of them). "loop": a member of a loop's queue (then use enqueue_task). "subtask": armed every "every" runs of parent_task_id.
every_daysNoStrict interval: due every N days, counted from start_date (the anchor; defaults to today in the user's time zone). A missed day does not shift the cycle. Schedule tasks/loops only, and instead of dow and cron (send dow 0 / cron null with it). null removes it.
start_dateNoFirst day it applies, YYYY-MM-DD; with every_days, the first day of the interval. null clears it.
descriptionNoLonger notes.
parent_task_idNoSubtasks: the parent task's id.
task_missed_behaviorNoSchedule tasks: what happens when a due day passes unchecked. "reschedule" keeps it armed, "drop" skips it automatically (abortions +1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and not-read-only, so the safety profile is covered. The description nonetheless adds the key trait those hints cannot express: this is a partial (PATCH-style) update where unspecified fields are preserved and only passed fields are overwritten. It omits consequences such as what happens when task_type is switched, but the added semantic is substantive.

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

Conciseness5/5

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

Two short sentences with zero filler; the partial-update rule is front-loaded and the overwrite consequence immediately follows.

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 13-parameter destructive mutation, the description says nothing about permissions, side effects of switching task_type, or how validation errors surface; it leans entirely on an unusually rich schema and the annotations. Adequate, but not sufficient on its own for a risky multi-field 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 description coverage is 100% and the field notes already spell out bitmask dow, cron/every_days exclusivity and task_type meanings. The description adds no field-level meaning beyond "the fields you pass", so it sits at the schema-covered baseline.

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?

"Change a task's fields" is a clear verb+resource, and the second sentence pins down partial-update semantics. It does not distinguish itself from siblings such as update_loop or create_task, so an agent must infer that task_id selects this tool over the loop variant.

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 context is only implied: the word "Change" signals existing tasks must be modified rather than created, and the schema's task_id note points at list_tasks/todays_tasks as the source of ids. There is no explicit when-not guidance (e.g., use create_task for new tasks, enqueue_task for loop membership), so routing depends on inference.

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