Skip to main content
Glama

complete_task

Idempotent

Marks a task as done and notifies the task's people, matching the web app's completion behavior.

Instructions

Mark a task done (notifies the task's people, like the web 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": {
      "task_id": "<task_id>"
    },
    "name": "complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations supply the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true) and flag openWorldHint=true, but they do not say what the external effect is. The description fills that gap by disclosing that completing a task notifies the task's people, which is a meaningful, non-obvious side effect that matters before calling. It does not say whether notifications can be suppressed or who exactly is notified, keeping it short of a 5.

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?

A single short sentence with the action front-loaded and the important side effect placed immediately after. The colloquial 'like the web app' is slightly loose but does convey behavioral parity efficiently.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and the notification side effect is covered. What remains missing is any hint about the task_id parameter's expected form and whether completion is reversible via reopen_task, which leaves the definition adequate but incomplete for a state-changing tool.

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 description coverage is 0% and the description never mentions task_id, so an agent gets no help on what identifier format is expected or where to source it. With one undocumented parameter, the description fails to compensate for the schema gap.

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?

The description gives a concrete verb+resource pair ("mark a task done") that an agent can act on directly, and the inverse operation (reopen_task) is implicitly distinguished by 'done'. It stops short of explicitly contrasting itself with sibling mutation tools like update_task or set_task_progress, but the core purpose is unambiguous.

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 explicit when-to-use or when-not-to-use guidance, no stated prerequisites, and no routing to alternatives such as reopen_task or update_task. The parenthetical 'like the web app' hints at behavioral parity but does not tell the agent under what conditions to choose this tool.

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