Skip to main content
Glama

Update To Do Task

update_todo_task
Destructive

Updates a Microsoft To Do task's title, notes, status, due date, importance, categories, or recurrence so you can keep task details current.

Instructions

Update a To Do task

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": {
      "list_id": "<list_id>",
      "task_id": "<task_id>"
    },
    "name": "update_todo_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoNew body/notes
titleNoNew title
statusNoStatus: notStarted, inProgress, completed, waitingOnOthers, deferred
list_idYesTo Do list ID
task_idYesTask ID
due_dateNoNew due date (ISO format). On a repeating task this moves the series to start on that date; To Do puts it on the first date the pattern allows from there. Must match recurrence.start_date if both are given
categoriesNoReplace the task's categories with these names. Pass [] to clear them
importanceNoImportance: low, normal, or high
recurrenceNoReplace the repeat pattern
clear_recurrenceNoRemove the repeat pattern, making the task one-off

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known, yet the description adds nothing beyond it. It does not disclose that unspecified fields are left untouched while categories and recurrence are replaced wholesale, nor that clear_recurrence removes a pattern — behavior an agent would need before calling a flag marked destructive.

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?

A single short sentence is technically concise with no wasted words, but it is under-specified rather than efficient. Nothing is front-loaded because nothing of substance is said.

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

Completeness1/5

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

For a 10-parameter mutation tool with a deep nested recurrence object and no output schema, the description supplies none of the semantic context needed to invoke it correctly. An agent cannot tell from this definition which fields are partial vs replaced, or what the destructive annotation implies.

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 10 parameters (including the nested recurrence object) are documented in detail in the schema itself. The description contributes no additional meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update a To Do task" restates the tool name and title almost verbatim, giving only a generic verb+resource. It does not differentiate this tool from siblings like set_todo_task_state or update_planner_task, nor does it say that this is a partial-field update to an existing To Do 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 when-to-use guidance, no mention of alternatives such as set_todo_task_state (for state changes only) or update_planner_task (for Planner tasks), and no prerequisites or exclusions. The agent must infer selection from the name alone.

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

Deploy Server

Other Tools