Skip to main content
Glama
Sign In

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

To Do Complete Task

todo_complete_task
Destructive

Marks a Microsoft To Do task as complete. It works through Apple Reminders, which syncs with To Do when the Microsoft account is added to Reminders, so the change appears in To Do after the next sync. Prefer task_id from todo_list_tasks. With title instead, it completes the one open task whose title contains that text (case-insensitive); if several match, it completes NONE and lists them with their task_id. Without list it searches every Reminders list, not only the To Do ones. With a Microsoft 365 account connected it uses Microsoft To Do directly (Microsoft Graph), with no Reminders sync.

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

Input Schema

NameRequiredDescriptionDefault
listNoList name to narrow search by title (optional)
titleNoTask title (partial match, alternative to task_id)
accountNoWhich connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.
confirmNoIgnored; kept for older clients.
task_idNoTask ID from todo_list_tasks

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to complete"New value: +"Ignored; kept for older clients."
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=false): it explains the Apple Reminders indirection, that changes appear only after the next sync, that an M365 account connected switches to Microsoft Graph with no sync, and crucially that ambiguous title matches complete NOTHING and return candidates.

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?

Front-loads the purpose, then adds sync caveat, parameter preference, ambiguity behavior, scope, and backend switch in a compact sequence. Every sentence carries information an agent would otherwise have to guess.

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

Completeness5/5

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

Given an output schema exists, return-format detail is unnecessary, yet the description still explains the one non-obvious return case (ambiguous matches list task_ids). Nothing needed to call this destructive, sync-delayed tool correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real semantics: which parameter is preferred, that title is a case-insensitive substring match, and that omitting list broadens the search beyond To Do lists. It does not restate the account or confirm parameters, which the schema already covers.

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?

States a specific verb and resource ("Marks a Microsoft To Do task as complete") and immediately pins down the backend path, distinguishing it from siblings like complete_reminder, complete_omnifocus_task, and todoist_complete_task without needing the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: prefer task_id from todo_list_tasks, otherwise use title as partial case-insensitive match, and use list to narrow. It also states the fallback source tool and the no-list case that searches every Reminders list.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources