Skip to main content
Glama

Complete task

complete_task
Idempotent

Mark a task as done (or set done=false to reopen it). On a repeating occurrence only that day is ticked off. Completing tasks can unlock apps if the user uses Task Lock. Can be reverted with undo_last_change.

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": {
      "id": "<id>"
    },
    "name": "complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask id from get_week, list_tasks or search_tasks (also "repeat_…" ids of repeating occurrences).
doneNotrue = done (default), false = not done.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: repeating occurrences tick off only that day, completing can unlock apps under Task Lock, and the change is revertible via undo_last_change. These are exactly the side effects and scope caveats an agent needs, and they are consistent with destructiveHint=false and idempotentHint=true.

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?

Three short sentences, each carrying distinct information: the primary action and its inverse, the repeating-occurrence scope, and the Task Lock side effect plus revert path. Nothing is redundant or buried.

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 two-parameter mutation with no output schema, the description covers the important non-obvious behavior (side effect, repeating scope, reversibility). The only gap is that it does not say what the response returns or how it relates to the plural complete_tasks sibling.

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 would be 3, but the description adds meaning: done=false is framed as reopening rather than merely "not done," and the repeating-occurrence sentence clarifies how the id behaves for "repeat_…" ids. This is useful semantics layered on top of the schema.

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?

States a specific verb and resource ("Mark a task as done") and adds the inverse operation (done=false reopens), so the action is unambiguous. It does not distinguish itself from the sibling complete_tasks, which likely handles bulk completion, leaving the agent to guess which to pick.

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?

Clear context for when to call it: to tick a task off, or to reopen it via done=false. It also names undo_last_change as the recovery path, which is real alternative guidance. It stops short of explicitly steering the agent toward complete_tasks for multi-task completion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources