Skip to main content
Glama

Microsoft Todo

by io.github.pipeworx-io

List Tasks

list_tasks
Read-onlyIdempotent

List the tasks in a Microsoft To Do list. Returns compact task summaries (title, status, importance, due date, created/completed times, and a body preview). Optionally filter by status. Use to browse a user's to-do list and see what tasks or reminders it contains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMaximum number of tasks to return (default 50, max 100).
statusNoOptional filter restricting results to tasks with this status.
list_idYesThe ID of the Microsoft To Do task list to read (from list_task_lists).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description only needs to add context. It adds useful behavioral detail about the return format (compact task summaries with specific fields) and optional status filtering. No contradiction with 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 fluff. The primary action is front-loaded, followed by return format and usage context. Every sentence earns its place.

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?

This is a simple read-only listing tool. The description covers purpose, return shape, and use case; the schema fully documents parameters; annotations cover safety. Nothing critical is missing for an agent to invoke 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?

All three parameters are fully described in the schema (100% coverage), so the description adds minimal semantics beyond the schema. 'Optionally filter by status' aligns with the status parameter but does not introduce new meaning; the baseline of 3 is appropriate.

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 ('List') and resource ('tasks in a Microsoft To Do list'), and clarifies the return shape with compact task summaries. It is clearly distinct from siblings like get_task (single task) but does not explicitly reference them, so it falls short of a 5.

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?

Provides clear context: 'Use to browse a user's to-do list and see what tasks or reminders it contains.' It does not explicitly mention alternatives or exclusions (e.g., use get_task for a single task), but the intended use case is clear.

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

All Microsoft Todo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation1/5

The set is dominated by overlapping Pipeworx and prediction-market tools, with ask_pipeworx and ask_pipeworx_beta explicitly described as currently identical, and ask_pipeworx_grounded, deep_research, and discover_tools serving heavily overlapping lookup purposes. The four Microsoft To Do tools are buried among 31 unrelated tools, making it very hard for an agent to select the right tool for the server's apparent domain.

Naming Consistency2/5

Most names are snake_case, but the naming conventions are otherwise mixed: there are verb_noun tools like list_tasks and get_task, bare verbs like remember/forget/recall, prefixed families like polymarket_*, and noun-phrase names like entity_profile, recent_changes, and pipeworx_trending. The lack of a consistent pattern across the set, especially relative to the Microsoft To Do server name, makes naming unpredictable.

Tool Count1/5

35 tools is already heavy, but the bigger problem is that only 4 of them are for Microsoft To Do, the server's stated name and purpose. The remaining 31 tools belong to unrelated Pipeworx data, prediction-market, and memory-management domains, which is an extreme scope mismatch.

Completeness1/5

For a Microsoft To Do server, the surface is severely incomplete: list_task_lists, list_tasks, get_task, and find_due_tasks cover reading and browsing only, with no create, update, complete, or delete operations. Even the broader Pipeworx functionality is scattered and redundant rather than forming a coherent domain surface.

Resources