Skip to main content
Glama

reopen_task

Move a completed task back to 'To Do' by ID or title; searches completed tasks so you can restore and resume work.

Instructions

Move a completed task back to 'To Do'. Identify it by id or title (searches done tasks too).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reopen_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoTask id — full UUID or a unique prefix (as shown in list_tasks, e.g. 'a1b2c3d4').
titleNoTask title — exact (case-insensitive) or a unique partial match. Use instead of id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the key behavioral fact — the task's target state is 'To Do' and the search includes already-completed tasks — but says nothing about what happens to completion history, subtasks, or whether the call fails when the task was never completed. Adequate but thin for an unannotated mutation.

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 action and target state, followed by the identification note. Nothing is wasted and nothing is 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, no-output-schema, unannotated tool, this covers purpose, target state, and lookup semantics. Only the failure modes and side effects of reopening are unstated, which is a modest gap given the tool's simplicity.

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 both parameters are already documented, making 3 the baseline. The description goes slightly beyond by noting that title matching reaches done tasks, which affects how an agent should phrase a lookup, though it doesn't add format or disambiguation detail.

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?

Specific verb plus resource plus state transition: "Move a completed task back to 'To Do'." It names the inverse of complete_task without ambiguity, and adds the identification modes, so an agent can immediately tell this is the undo counterpart to task completion.

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?

Usage context is clear — this is the tool for undoing completion, implicitly contrasted with complete_task. The parenthetical "searches done tasks too" clarifies the retrieval scope. What's absent is any explicit exclusion, such as what to do if the task was never completed or which sibling to prefer when the intent is ambiguous.

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