Skip to main content
Glama

graph_list_todo_lists

Lists Microsoft To Do task lists and returns their IDs for use in other To Do operations, with paging via top, skip, or nextLink.

Instructions

List Microsoft To Do task lists.

Use the returned list IDs with the other To Do tools.

Args: top: Maximum number of lists to return (default 25, maximum 50). skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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": "graph_list_todo_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the server-side cap of 50 items per call, how to page (raise skip in steps of top), that next_link overrides the other paging arguments, and that include_next_link changes the return shape. It omits any mention of permissions/scopes or result ordering.

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?

Front-loaded with the purpose, then a well-structured Args block where each line adds information. Slightly verbose in the include_next_link sentence and a mid-sentence parenthesis, but nothing is wasted.

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

Completeness4/5

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

For a 4-optional-parameter list tool with no annotations and no output schema, the description covers paging controls and the two return shapes, which is the critical unknown. It does not describe the fields of a returned list object, a minor residual gap.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates: top (default 25, max 50 – correcting the schema's far larger maximum), skip (default 0 and paging behavior), next_link (opaque URL, overrides other paging args), and include_next_link (bare list vs {items, next_link}). Every parameter's meaning and interaction is spelled out.

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?

"List Microsoft To Do task lists" gives a specific verb and resource, and the follow-up sentence ties the output (list IDs) to the rest of the To Do tool family. It is clear apart from graph_list_todo_tasks, though it never explicitly contrasts the two.

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?

"Use the returned list IDs with the other To Do tools" supplies a clear downstream-use context, and the paging notes explain when to use skip vs next_link. It stops short of exhaustive when-to-use/when-not guidance or naming an alternative sibling.

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