Skip to main content
Glama

Create To Do List

create_todo_list

Creates a new private Microsoft To Do list with a specified name; use it to organize tasks, then share the list in the To Do app if needed.

Instructions

Create a new To Do list. Graph cannot share a list — the new list is private until someone shares it in the To Do app

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "display_name": "<display_name>"
    },
    "name": "create_todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
display_nameYesName of the list. Must not match an existing list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only tell the agent this is a non-read-only, non-destructive write. The description goes further with a genuinely non-obvious behavior: Graph cannot share a list, so the new list stays private until shared inside the To Do app. That is real behavioral context an agent cannot get from the schema or annotations, though return/error behavior is still unstated.

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?

Two sentences, front-loaded with the action, and the second carries non-redundant privacy information. The phrasing 'Graph cannot share a list' is slightly terse and could confuse an agent unfamiliar with the Graph/To Do split, 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 one-parameter create tool with annotations and full schema coverage, the description covers what the tool does and the privacy consequence of creation. Only duplicate-name failure handling is left implicit via the schema rather than stated outright.

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?

There is only one parameter and the schema documents it at 100% coverage, including the 'must not match an existing list' constraint. The description adds no meaning beyond the schema for display_name, so the baseline 3 applies.

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?

Names a specific verb and resource ('Create a new To Do list'), which is unambiguous. It does not explicitly contrast with siblings like create_todo_task or create_planner_task, but the 'list' object is stated clearly enough to distinguish it.

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?

Usage is implied by the create verb — an agent knows to call this when a new list is needed. However, there is no explicit when-to-use/when-not context, no mention of preconditions (e.g., duplicate names will fail), and no routing to alternatives.

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