Skip to main content
Glama
MAG-Cie

MCP for Microsoft To Do

list_tasks_by_category

Read-only

Lists all tasks containing a specified category across every list in Microsoft To Do, using an OData filter.

Instructions

List ALL tasks containing a given category, across every list. OData filter: categories/any(c: c eq '...').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
top_per_listNo
include_completedNo
verboseNoIf true: returns full JSON. Otherwise: compact text format (default, saves tokens).

Implementation Reference

  • Actual implementation of listTasksByCategory. Fetches all task lists, builds an OData filter for the given category (and optionally excludes completed tasks), then fetches tasks across all lists via fetchTasksAcrossLists.
    export async function listTasksByCategory(
      category: string,
      opts: { topPerList?: number; includeCompleted?: boolean } = {}
    ): Promise<SearchResult[]> {
      const lists = await listTaskLists();
      const escaped = category.replace(/'/g, "''");
      const filterParts = [`categories/any(c: c eq '${escaped}')`];
      if (!opts.includeCompleted) filterParts.push("status ne 'completed'");
      const filter = filterParts.join(" and ");
      const perList = await fetchTasksAcrossLists(lists, {
        filter,
        top: opts.topPerList ?? 50,
      });
      return perList.flatMap(({ list, tasks }) =>
        tasks.map((task) => ({
          list: { id: list.id, displayName: list.displayName },
          task,
        }))
      );
    }
  • Zod schema for list_tasks_by_category input validation: requires a 'category' string, with optional 'top_per_list' (positive int ≤100), 'include_completed' (boolean), and verbose fields.
    list_tasks_by_category: z.object({
      category: z.string().min(1),
      top_per_list: z.number().int().positive().max(100).optional(),
      include_completed: z.boolean().optional(),
      ...verboseField,
    }),
Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds useful context: it lists all tasks across every list and mentions the OData filter syntax. However, it does not disclose potential limits like pagination or the effect of top_per_list on 'ALL tasks'.

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?

The description is very concise (two sentences), front-loading the purpose and providing a useful OData syntax hint. However, it could be slightly more structured to cover all parameters without becoming verbose.

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

Completeness2/5

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

With 4 parameters and no output schema, the description inadequately explains top_per_list and include_completed, and creates ambiguity with 'ALL tasks'. It fails to clarify the output format beyond the verbose parameter's schema description.

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?

Only the verbose parameter has a description in the schema (25% coverage). The description adds OData filter details for category but fails to explain top_per_list and include_completed. Moreover, 'List ALL tasks' contradicts the limiting effect of top_per_list.

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 the verb (list) and resource (tasks), specifies scope (across every list), and provides the OData filter syntax. It distinguishes itself from siblings like list_all_tasks or search_tasks by focusing on category filtering.

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?

The description implies when to use (when filtering by category) but does not explicitly mention when not to use or suggest alternatives like list_all_tasks or search_tasks for other filtering needs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MAG-Cie/mcp-microsoft-todo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server