Skip to main content
Glama

get_task

Read-onlyIdempotent

Retrieve a single Kaiten task by card ID, optionally including its description body text, so AI assistants can inspect task details.

Instructions

Get one task. Set include_description=true for body text.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYes
include_descriptionNo

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
laneNo
tagsNo
boardNo
stateNo
titleYes
columnNo
createdNo
lane_idNo
type_idNo
updatedNo
_metricsNo
board_idNo
due_dateNo
owner_idNo
column_idNo
conditionNo
truncatedNo
propertiesNo
sort_orderNo
descriptionNo
external_idNo
responsible_idNo
description_charsNo
description_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only one behavioral detail beyond that: that body text is opt-in via include_description, which matters for payload size. It says nothing about error behavior for a missing card_id or pagination.

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 with zero waste, and the core action is front-loaded before the parameter hint. Nothing is padded or repeated.

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?

An output schema exists, so return values need not be described. For a two-parameter read tool with full annotation coverage, the definition is close to sufficient; the remaining gap is the undocumented card_id semantics and missing-record behavior.

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?

Schema description coverage is 0%, so the description carries the burden and only partially discharges it. It explains include_description ("for body text"), which is genuinely useful since the parameter name alone is ambiguous about what text is included, but card_id is left entirely to the name.

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 uses a specific verb and resource ("Get one task") and the word "one" implicitly distinguishes it from list_tasks in the sibling set. It does not name an alternative explicitly, so it stops short of 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the single-item retrieval path when it already has a card_id, and the include_description hint gives one conditional cue. There is no explicit when-to-use or when-not-to-use guidance relative to list_tasks or get_task_tags.

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