Skip to main content
Glama
Sign In
Microsoft To Do MCP

Microsoft To Do MCP

by jordanburke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get-tasks

Retrieve tasks from a specified Microsoft To Do list to review main to-do items and their checklist subtasks, with optional filtering, sorting, pagination, and count.

Instructions

Get tasks from a specific Microsoft Todo list. These are the main todo items that can contain checklist items (subtasks).

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": {
      "listId": "<listId>"
    },
    "name": "get-tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoMaximum number of tasks to retrieve
skipNoNumber of tasks to skip
countNoWhether to include a count of tasks
filterNoOData $filter query (e.g., 'status eq \'completed\'')
listIdYesID of the task list
selectNoComma-separated subset of the shown fields to include: status, dueDateTime, importance, categories, recurrence, body (e.g., 'status,dueDateTime'). id and title are always included; other names are ignored.
orderbyNoProperty to sort by (e.g., 'createdDateTime desc')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / select / description
      Previous value: -"Comma-separated list of properties to include (e.g., 'id,title,status')"New value: +"Comma-separated subset of the shown fields to include: status, dueDateTime, importance, categories, recurrence, body (e.g., 'status,dueDateTime'). id and title are always included; other names are ignored."
  2. First observedv1.1.3

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it: no mention of read-only nature, pagination defaults, result ordering, or what happens with a large list. The only behavioral clue is the parent/child note about checklist items.

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?

Two short sentences, front-loaded with the action and resource, with no filler. The second sentence adds real context about what the returned items are.

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 7-parameter list tool with no annotations or output schema, the description covers the core intent and item hierarchy but says nothing about pagination behavior, default result size, or shape of returned tasks. Adequate minimum, but leaves meaningful gaps.

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%, so top, skip, count, filter, select and orderby are fully documented in the schema; the description adds no parameter meaning beyond that. Baseline 3 applies.

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?

States a specific verb and resource ('Get tasks from a specific Microsoft Todo list') and clarifies the item hierarchy — that these are parent items containing checklist subtasks — which helps distinguish it from get-checklist-items. It lacks an explicit contrast with sibling get-task-lists, but the resource is unambiguous.

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 only implied: 'from a specific list' hints that listId must be known first, but the description never says when to call this versus get-checklist-items, get-task-lists, or filter-based retrieval. No exclusions or prerequisites are stated.

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