Skip to main content
Glama

reopen_task

Idempotent

Marks a completed task as unfinished again so you can resume work, correct mistaken completion, or reopen it for follow-up.

Instructions

Mark a done task as not done again.

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": "reopen_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/5.0
Behavior2/5

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

Annotations already declare the operation non-read-only, idempotent, non-destructive and open-world, so the core safety profile is covered. The description adds nothing beyond that: it does not say whether completion dates/history are cleared, whether progress values are reset, or what happens if the task is not done.

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 with no waste and the key precondition front-loaded. It is perhaps overly terse for a state-mutating tool, but nothing is redundant.

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?

The output schema covers return values and annotations cover safety, so the biggest remaining gaps are the undocumented task_id and the unstated side effects on completion metadata. For a simple single-parameter mutation, this is adequate but not thorough.

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% for the single required task_id, and the description never mentions it or its expected format. The agent must infer that task_id refers to the task being reopened.

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 sentence states a specific action and its precondition: converting a done task back to not-done. This is a recognizable inverse of complete_task, though the description never names that sibling or any other tool, leaving differentiation implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The precondition ('a done task') implies when to use it, and the existence of complete_task makes the pairing obvious. However, there is no explicit guidance on alternatives (e.g. update_task) or on what to do for non-done tasks.

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