Skip to main content
Glama

Create To Do Task

create_todo_task

Create a Microsoft To Do task in a list, optionally recurring, with due date, notes, categories, and source tagging. Safe retries avoid duplicates when the external ID exists.

Instructions

Create a new To Do task, optionally recurring. With linked_resource, the task is tagged with its source, and a create whose external_id is already on a task in the list returns that task instead of a second copy, so a retry is safe. That check reads the whole list first

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

Input Schema

NameRequiredDescriptionDefault
bodyNoTask body/notes
titleYesTask title
list_idYesTo Do list ID
due_dateNoDue date (ISO format). Required when recurrence is set
extensionNoYour own data on the task, which the person can't see or edit
categoriesNoCategory names, matching the person's Outlook categories
importanceNoImportance: low, normal, or high
recurrenceNoRepeat pattern. Omit for a one-off task
linked_resourceNoTag the task with where it came from. Stored as the task's linkedResources

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, it discloses a non-obvious behavioral trait: creates with an already-seen external_id return the existing task rather than creating a duplicate, making retries safe. It also warns that this dedupe check reads the whole list first, which is useful performance context an agent would not otherwise know.

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?

Three sentences, front-loaded with the core action and free of filler. The closing 'That check reads the whole list first' is terse and slightly ambiguous about what list is meant, but still earns its place by flagging a performance characteristic.

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 nine-parameter create tool with nested recurrence and linked_resource objects, the description covers the key non-obvious semantics: recurrence, source tagging, idempotency, and the list-read cost. It does not describe the return value, but no output schema exists and the schema itself is richly documented.

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 100%, so the baseline is 3, but the description adds meaning by explaining that linked_resource/external_id drives dedupe behavior and that recurrence is optional. It does not add further syntax detail for the nested recurrence object, which the schema already documents thoroughly.

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 first sentence states a specific verb and resource ('Create a new To Do task') and immediately adds the optional-recurrence scope. The 'To Do' qualifier cleanly separates it from siblings like create_planner_task and create_todo_list without needing to name them.

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?

The description gives clear usage context for linked_resource: it tags the source and makes retries safe by returning an existing task with the same external_id. It does not explicitly contrast with update_todo_task or state when not to use this tool, but the create/retry guidance is concrete.

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