Skip to main content
Glama

reopen_task

Reopen a closed Kanboard task using its task ID so work can continue on a previously completed item.

Instructions

Reopen a closed task.

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_idYesKanboard task ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is carried by structured data. The description adds the meaningful precondition that only closed tasks are valid targets, but says nothing about side effects (clearing completion date, notifications, assignee state) or failure behavior for a non-closed task.

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?

One short sentence, zero filler, and the key information (action plus applicable state) is front-loaded. Nothing could be cut without losing content.

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?

An output schema exists and annotations cover safety, and the single parameter is fully documented, so the agent has enough to call the tool. What remains missing is behavioral context around the state transition and error cases, which matters for a mutation tool with openWorldHint=true.

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?

With a single parameter at 100% schema description coverage, the schema already explains task_id as a positive Kanboard task ID. The description adds no meaning beyond that, so the baseline 3 applies.

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?

"Reopen a closed task" gives a specific verb (reopen) and resource (task) plus the state constraint, so an agent can distinguish it from siblings like close_task or update_task without opening the schema. It stops short of an explicit contrast with those alternatives, which keeps it from 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 Guidelines2/5

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

There is no explicit when-to-use guidance beyond the implied "a task is closed and needs to be active again." Nothing states prerequisites (permissions, project state), what happens if the task is not closed, or why one would choose this over update_task with a status field.

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