Skip to main content
Glama
Sign In
Task Queue MCP

Task Queue MCP

by devops-riku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Complete a task

complete_task

Marks an in-progress task as finished, recording a completion note and end time. Resume a paused task before completing it; tasks blocked for a reason must be resumed in Task Queue.

Instructions

Completes a task in progress (a paused one is resumed first). A task blocked for a reason must be resumed in Task Queue.

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

Input Schema

NameRequiredDescriptionDefault
noteNoThe completion note: what was done.
taskYesThe task: its number, e.g. TASK-000123, or its id.
ended_atNoWhen work ended, ISO 8601 with a UTC offset, e.g. 2026-11-13T09:30:00+08:00. Default: now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and readOnlyHint=false, so the description's job is to add side-effect detail — and it does, disclosing that a paused task is resumed first (an implicit mutation beyond 'complete') and that blocked tasks cannot be completed here. It does not say what happens if the task is already complete, but the main surprise is covered.

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?

Two short sentences, front-loaded with the core action and immediately followed by the one caveat that changes agent behavior. No filler or restatement of the title.

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?

For a mutation tool with no output schema, the definition covers input well but is silent on outcomes — what is returned, whether completion is idempotent, or what happens to an already-completed task. Adequate, but with a clear remaining gap.

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%, including the TASK-000123/id format and the ISO 8601 ended_at default, so the schema carries parameter meaning. The description adds nothing about note or ended_at, leaving this at the baseline 3.

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 ('Completes a task in progress') and clarifies the paused-task nuance, which distinguishes it from pause_task/resume_task/start_task behaviorally. It stops short of naming a sibling it is not, so it lands just below a 5.

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?

Gives a real precondition: paused tasks are resumed automatically, but a task blocked for a reason must be resumed in Task Queue instead, which tells the agent when this tool will not work. There is no explicit routing between this and delete_task/move_task/update_task, but the key exclusion is stated.

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

Deploy Server

Other Tools