Skip to main content
Glama

Complete Task

complete_task

Mark a task as completed by task ID, with optional completion notes and project root path.

Instructions

Mark a task as completed with optional notes.

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
pathNoProject root directory..
notesNoCompletion notes.
task_idYesThe task ID to complete.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/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 burden of behavioral disclosure. It states the mutation but not whether completion is reversible, what happens to notes (persisted into project context?), whether dependents or phase progress are affected, or whether any permission/session state is required.

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?

One short sentence, front-loaded with the action and resource, with no wasted words. It is arguably too terse rather than too long, but structurally sound.

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?

For a state-mutating tool in a project-brain workflow with zero annotation coverage, the description is thin: it omits reversibility, interaction with phase/task state, and when it is the right call versus update_task. The existing output schema and fully documented params reduce the burden somewhat, but not enough.

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 all three parameters including path and notes are already documented, which sets the baseline at 3. The description only restates the optional notes parameter and says nothing about the path argument or how notes are stored.

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 specific verb and resource ("Mark a task as completed") plus the notes option, so its function is unmistakable. It does not, however, differentiate itself from sibling tools such as update_task or complete_phase, which an agent could plausibly confuse it with.

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 statement of when this tool should be used versus update_task (which could likely also set status) or complete_phase. No prerequisites are given, such as whether the task must first be in progress or assigned.

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