Skip to main content
Glama

graph_update_todo_task

Update a Microsoft To Do task by changing only the fields you provide, including title, notes, due date, status, and importance. Set status to completed to mark the task done.

Instructions

Update a task in a Microsoft To Do list. Only the supplied fields are changed.

Complete a task by setting status to "completed".

Args: list_id: The task list ID (from graph_list_todo_lists). task_id: The task ID to update. title: New task title. notes: New plain-text notes for the task body. due_datetime: New due date and time (ISO 8601). timezone: Timezone for due_datetime (default "UTC"). status: New status: "notStarted", "inProgress", "completed", "waitingOnOthers", or "deferred". Empty leaves the status unchanged. importance: New importance: "low", "normal", or "high". Empty leaves the importance unchanged.

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

Input Schema

NameRequiredDescriptionDefault
notesNo
titleNo
statusNo
list_idYes
task_idYes
timezoneNoUTC
importanceNo
due_datetimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose key mutation semantics: only supplied fields change, empty strings leave status/importance unchanged, and timezone defaults to UTC. However, it omits whether the empty-string sentinel also applies to title, notes, and due_datetime (so clearing a field is undefined), and says nothing about permissions, reversibility, or error behavior for a write operation.

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?

The leading sentences state purpose and the partial-update contract before the parameter breakdown, so it is well front-loaded. The Args block is somewhat repetitive but justified given zero schema coverage; no sentence is filler.

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 an eight-parameter mutation tool with no annotations and no output schema, the definition covers the parameters and the core update semantics adequately. The main omission is what the call returns or how failures surface, which matters here because no output schema documents the response.

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 description coverage is 0%, so the description must compensate, and it does: all eight parameters are documented, including ISO 8601 format for due_datetime, the timezone default, the exact enum values for status and importance, and the provenance of list_id from graph_list_todo_lists. The gap is that empty-string behavior is spelled out only for status and importance, leaving title, notes, and due_datetime ambiguous when set to "".

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 in a Microsoft To Do list") and immediately clarifies scope with "Only the supplied fields are changed." It is clearly distinguishable from the create/delete/list To Do siblings by the verb alone, though it never names an alternative explicitly.

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

Usage Guidelines4/5

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

It gives concrete usage context, notably "Complete a task by setting status to 'completed'," which tells the agent how to achieve a common intent. It also signals the partial-update pattern, but offers no explicit exclusions or routing to siblings such as graph_create_todo_task or graph_delete_todo_task.

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