Skip to main content
Glama

graph_create_todo_task

Create a task in a Microsoft To Do list with optional notes, due date, reminder, and importance; requires Tasks.ReadWrite permission.

Instructions

Create a task in a Microsoft To Do list. Requires the Tasks.ReadWrite permission.

Empty fields are omitted from the created task.

Args: list_id: The task list ID (from graph_list_todo_lists). title: Task title. notes: Optional plain-text notes stored in the task body. due_datetime: Optional due date and time (ISO 8601, e.g. "2025-03-01T17:00:00"). timezone: Timezone for due_datetime and reminder_datetime (default "UTC"). importance: Task importance: "low", "normal", or "high" (default "normal"). reminder_datetime: Optional reminder date and time (ISO 8601).

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>",
      "title": "<title>"
    },
    "name": "graph_create_todo_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
titleYes
list_idYes
timezoneNoUTC
importanceNonormal
due_datetimeNo
reminder_datetimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose two genuinely useful behaviors: the Tasks.ReadWrite permission requirement and that empty fields are omitted from the created task. It omits what is returned (the created task object?), and whether reminder_datetime without due_datetime is dropped or rejected, which matters for a mutation tool at zero annotation coverage.

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 operation and permission come first, then the behavioral caveat, then a scannable Args list. Slightly redundant in restating schema defaults ("default 'UTC'", "default 'normal'") but otherwise tight with no 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 a seven-parameter mutation tool with no annotations and no output schema, the definition covers auth, field omission behavior, and every parameter. The remaining gap is the return value and failure behavior for an invalid list_id or malformed datetime, which an agent would want before invoking.

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 seven parameters get meaning, including ISO 8601 format with a concrete example for due_datetime, allowed importance values, the source of list_id, and that notes land in the task body. It stops short of explaining parameter interactions (timezone applying to two fields, reminder without due), leaving a small gap.

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?

The opening sentence names a specific verb (Create) and resource (a task in a Microsoft To Do list), which is enough to separate it from graph_create_event, graph_create_channel, and the other create_* siblings by resource type alone. The required permission (Tasks.ReadWrite) is stated immediately after.

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 create semantics, and the description gives a useful upstream pointer by noting list_id comes from graph_list_todo_lists. However, it never states when to prefer this over alternatives such as graph_update_todo_task, nor any precondition (e.g. that the target list must already exist).

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