Skip to main content
Glama

get_task

Read-only

Fetch everything about a Kanboard task—details, tags, subtasks, comments, and attachments—to summarize or review its progress.

Instructions

Get everything about a task: details, tags, subtasks, comments and attachments.

Use this to summarise or review a task's progress.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesKanboard task ID
max_commentsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile needs no restating. The description usefully discloses breadth of retrieval (comments and attachments included), but omits a meaningful behavioral trait: comments are capped by max_comments (default 30), so results can be silently truncated.

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?

Two short sentences with the retrieval scope front-loaded and the use case second; nothing is redundant. Slightly informal ("everything about a task") but efficient overall.

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, so return values need no explaining, and the tool is a read with only two parameters. However, the undefined max_comments parameter and the resulting truncation behavior are left unexplained, which is a real completeness gap for a tool whose value is exhaustive retrieval.

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 only 50%: task_id is documented as a Kanboard task ID, but max_comments has no schema description and is never mentioned in the description. The description therefore does not compensate for the gap, leaving the agent unaware that comment retrieval is bounded.

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 description states a specific verb and resource ("Get everything about a task") and enumerates the returned facets: details, tags, subtasks, comments and attachments. That contrasts implicitly with aggregate siblings like list_tasks, search_tasks and get_board, though no sibling is named explicitly.

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?

"Use this to summarise or review a task's progress" gives one clear use case, but there is no guidance on when not to use it or which sibling to prefer (e.g. search_tasks for discovery, list_tasks for bulk listing). Usage context is implied rather than fully framed.

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