Skip to main content
Glama

Complete a task

taskhold_complete
Idempotent

Mark a task or step done, with a summary of what you did and, optionally, a structured outcome: files changed (with +/- line counts), checks run (pass/fail/skip), links (PR, commit, branch, deploy, doc), follow-up task ids, risks and how the person can verify it. The person sees it as a What changed card; a step's outcome rolls up to its task. When the person should look at the work, pass needs_review: true with outcome.verify (how you checked it): the task lands in their Ready for review queue. Completing a step tells you the next one; start_next: true also starts it, and finish_task: true on the last open step closes the task too (with the same summary) in one call. For a step it returns steps done, the task's bar and the next step's id (or, after the last step, a reminder to complete the task). Completing a task closes its open steps. Repeating it on a task that is already done changes nothing and keeps the first summary (add more with taskhold_add_note); an unknown task_id fails with "Task not found", an invalid outcome fails without changing anything.

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

Input Schema

NameRequiredDescriptionDefault
outcomeNoWhat changed, shown to the person as a What changed card (20 KB max). Every field is optional.
summaryNoWhat was done (and how you checked it). Markdown.
task_idYesThe ID of the task to complete
start_nextNoWhen completing a step, start the next step too (default false)
finish_taskNoWhen completing the last open step, also complete its task with this summary (default false)
needs_reviewNoAsk the person to review the work: the task goes to their Ready for review queue (it still counts as done). Needs outcome.verify, a short "how I checked it" line. They approve it or request changes; both arrive in taskhold_updates (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / outcome / properties / follow_ups / items / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description confirms the idempotent behavior in concrete terms ("Repeating it on a task that is already done changes nothing and keeps the first summary"), so they are consistent rather than additive. It does add genuinely new behavior beyond the annotations: the side effect of closing open steps, the step-to-task roll-up of outcomes, the Ready-for-review queue routing, and the specific failure modes ("Task not found", invalid outcome leaves state untouched).

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?

Front-loaded with the core action, then ordered by escalating options (outcome, review, step chaining, return values, edge cases). It is dense, with several long compound sentences and stacked parentheticals that could be split, but nearly every clause carries distinct operational information.

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?

With no output schema, the description correctly spells out return values ("steps done, the task's bar and the next step's id" plus the reminder after the last step), error behavior, and idempotency -- complete for a six-parameter mutation tool with nested objects. What is missing is minor: no mention of what happens when needs_review is passed without outcome.verify (rejected or silently ignored).

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description goes well past the schema by explaining interactions the schema cannot express: needs_review requires outcome.verify and lands the task in a review queue while still counting as done, and start_next/finish_task only take effect in specific step positions. The outcome is framed by its purpose (files with +/- counts, checks pass/fail/skip, links, follow-ups, risks) rather than restated.

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?

Opens with a specific verb+resource ("Mark a task or step done") and immediately distinguishes the two modes it handles: a step vs. a whole task. It also names the artifact the user sees ("a What changed card"), which separates it from sibling mutation tools like taskhold_update or taskhold_add_note.

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: use needs_review when "the person should look at the work", use start_next: true to begin the next step, finish_task: true on the last open step to close the task in one call. It even names the alternative for post-completion additions ("add more with taskhold_add_note"), which is precisely the when-not guidance this dimension rewards.

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