MCP for Microsoft To Do

list_overdue_tasks

Read-only

Aggregate all incomplete tasks past their due date from every Microsoft To Do list into a single view.

Instructions

List ALL overdue tasks (status ne completed and dueDateTime < today) across every list. Aggregated via Promise.all.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_overdue_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`top_per_list`	No
`verbose`	No	If true: returns full JSON. Otherwise: compact text format (default, saves tokens).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1May 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds that results are aggregated via Promise.all, hinting at parallel requests and potential performance characteristics. It could mention pagination or size limits, but adds value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The first sentence states purpose and filter, the second adds implementation detail. Front-loaded and efficient.

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?

The description is adequate for a simple list tool with annotations, but it lacks explanation of top_per_list and expected output format beyond the verbose parameter's schema description. Missing pagination info.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not explain top_per_list at all, leaving its meaning unclear. verbose is described in the schema, but with schema coverage at 50%, the description should compensate. It does not.

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 description clearly states 'List ALL overdue tasks' with explicit filter conditions (status ne completed and dueDateTime < today) and scope across every list. This distinguishes it from siblings like list_all_tasks, list_tasks, and search_tasks.

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 implies usage for retrieving all overdue tasks across all lists. It doesn't explicitly state when not to use or offer alternatives, but the name and filter make context clear.

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