Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

todo

Create and manage Microsoft task lists, tasks, and checklist items to organize work and track status, due dates, and reminders.

Instructions

Microsoft To Do: manage lists, tasks, and checklist items

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": {
      "operation": "<operation>"
    },
    "name": "todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoTask body content
titleNoTask title
listIdNoTo Do list ID
statusNoTask status
taskIdNoTo Do task ID
dueDateNoDue date (YYYY-MM-DD or ISO 8601)
isCheckedNoCheck/uncheck a checklist item
operationYesOperation to perform
importanceNoTask importance
maxResultsNoMax results (default: 50)
displayNameNoList or checklist item name
checklistItemIdNoChecklist item ID
reminderDateTimeNoReminder date/time in ISO 8601

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. 'Manage' implies mutation, but the presence of delete_list, delete_task, and delete_list-style irreversible operations, required auth scopes, and what deletion cascades to are all unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with zero filler, which is good, but it is undersized for a 13-parameter, 13-operation multiplexer. There is no structure enumerating the operation groups, so terseness here costs the agent usable information.

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?

Given high complexity (13 params, 13 operations, nested enum semantics), no annotations, and no output schema, one sentence is far short of complete. An agent cannot learn from the description which operations exist, what they return, or which parameter sets pair with which operation.

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%, so every one of the 13 parameters is already documented in the schema, which sets the baseline at 3. The description adds nothing, and notably omits the operation-to-parameter mapping (e.g., that taskId only applies to task operations) that an agent must infer from the enum list alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the product and the three resource types (lists, tasks, checklist items) it covers, so the general domain is identifiable. But 'manage' is a generic verb that never states the tool exposes 13 discrete operations, and it gives no differentiation from the sibling 'planner', which is another task-management surface an agent must choose between.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing tells the agent when to pick this over 'planner', 'calendar', or 'search', nor which operation to select for a given intent. The one-line description supplies context by implication only.

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