Skip to main content
Glama
MAG-Cie

MCP for Microsoft To Do

delete_extension

DestructiveIdempotent

Remove an open extension from a Microsoft To Do task by specifying the list ID, task ID, and extension name.

Instructions

Delete an open extension from a task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
task_idYes
extension_nameYes

Implementation Reference

  • The actual Graph API function that performs the DELETE HTTP request to Microsoft Graph to remove an open extension from a task. It sends a DELETE to /me/todo/lists/{listId}/tasks/{taskId}/extensions/{extensionName}.
    export async function deleteTaskExtension(
      listId: string,
      taskId: string,
      extensionName: string
    ): Promise<void> {
      await graphFetch<void>(
        `/me/todo/lists/${enc(listId)}/tasks/${enc(taskId)}/extensions/${enc(extensionName)}`,
        { method: "DELETE" }
      );
    }
  • Zod validation schema for the delete_extension tool. Defines the required arguments: list_id (string), task_id (string), and extension_name (string with length 1-120, matching regex for valid characters).
    delete_extension: z.object({
      list_id: z.string(),
      task_id: z.string(),
      extension_name: z
        .string()
        .min(1)
        .max(120)
        .regex(/^[A-Za-z0-9._-]+$/, "extension_name: only letters, digits, '.', '_', '-' allowed"),
    }),
Behavior3/5

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

Annotations already provide destructiveHint and idempotentHint. Description adds 'open extension' specifier but no additional behavioral context beyond 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?

Single sentence, direct, no redundancy. Every word adds value.

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?

Missing context: no guidance on how list_id or task_id are used, no return behavior, no error cases. For a destructive tool, description is incomplete without parameter details.

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?

Schema coverage is 0%, and description does not explain parameters (list_id, task_id, extension_name). Only mentions 'open extension' implicitly tying to extension_name.

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?

Description clearly states it deletes an open extension from a task, effectively distinguishing from sibling tools like set_extension and list_extensions.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., delete_task). The purpose is implied but no when-not-to-use or alternatives mentioned.

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