Skip to main content
Glama

close_task

Marks a Kanboard task as complete using its task ID, with the option to reopen it later if needed.

Instructions

Close (complete) a task. It can be reopened with reopen_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": "close_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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is partly covered; the description adds the meaningful behavioral fact that the effect is reversible via reopen_task. It does not explain what closing changes beyond status (board column, timestamps, notifications), which keeps it below a 5.

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, action and reversibility front-loaded, with no redundant restatement of the title or schema. Nothing could be removed without losing 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 annotations covering the safety profile and an output schema handling return values, the description only needed to state the action and its reversibility, which it does. A brief note on side effects (status/board movement) would make it fully complete for a mutation tool.

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?

There is a single required parameter at 100% schema coverage, with the schema already describing it as a positive Kanboard task ID. The description adds no meaning about the identifier or any failure modes (invalid or already-closed task), so 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?

Names a specific verb+resource ('Close (complete) a task') and disambiguates 'close' with the parenthetical 'complete', so the agent knows this is status completion rather than file/connection closing. It also implicitly separates itself from reopen_task, the inverse operation.

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 sentence 'It can be reopened with reopen_task' gives a recovery path and points to the sibling that undoes this operation, which is useful when-to-use context. However, it never states prerequisites or when not to close a task (e.g. blocked or unassigned tasks), so guidance is implied rather than explicit.

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