Skip to main content
Glama
Sign In
sam2kb

m365-mcp

by sam2kb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

m365_tasks_list

Read-onlyIdempotent

Retrieve tasks from a Microsoft To Do list by list ID, newest first, including status, importance, due dates, and notes, with optional filters and a total-result cap.

Instructions

List tasks inside one Microsoft To Do list, newest created first. Returns IDs, status, importance, due dates and notes limited to 500 characters; top caps total results across internal pages. Use m365_tasks_lists to find list IDs, m365_tasks_create to add tasks, or m365_tasks_update to change or complete one.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum total tasks to return, not page size
filterNoOData filter, e.g. status ne 'completed'
listIdYesTask list ID (from m365_tasks_lists)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.1
    • changedInput schema / properties / top / description
      Previous value: -"Max tasks"New value: +"Maximum total tasks to return, not page size"
  2. Changed3 schema fields changedv1.2.0
    • addedInput schema / properties / top / maximum
      Added value: +500
    • addedInput schema / properties / top / minimum
      Added value: +1
    • changedInput schema / properties / top / type
      Previous value: -"number"New value: +"integer"
  3. First observedv1.0.7

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is lifted; the description adds real value with result ordering, returned field inventory, the 500-character notes truncation, and the fact that top caps total results across internal pages rather than page size. It does not mention error behavior or permission scope, keeping it short of a 5.

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, zero filler: the first establishes scope, ordering, and return contents; the second handles sibling routing. The core operation is front-loaded before alternatives.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the return fields and the truncation rule, and the truncation/paging cap ambiguity is resolved in prose. Combined with full schema coverage of all three parameters, an agent has everything needed to call it correctly.

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% and the schema itself explains top's 'maximum total, not page size' semantics and gives an OData filter example. The description restates the top paging behavior and names the source of listId, which is modest added value rather than new meaning, so baseline 3 applies.

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?

States a specific verb (list) and resource (tasks inside one Microsoft To Do list), plus ordering semantics (newest created first). An agent can distinguish it from m365_tasks_lists, m365_tasks_create, and m365_tasks_update without inspecting schemas.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use m365_tasks_lists to find list IDs, m365_tasks_create to add, m365_tasks_update to change or complete. The precondition for the required listId is spelled out, leaving no inference needed.

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