Skip to main content
Glama

create_task

Creates a Kaiten task or card on a specified board using a required title and board ID, with optional lane, column, assignee, due date, and description.

Instructions

Create a Kaiten task/card. Requires title and board_id.

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": {
      "title": "<title>",
      "board_id": "<board_id>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
lane_idNo
type_idNo
board_idYes
due_dateNo
owner_idNo
positionNo
column_idNo
descriptionNo
external_idNo
responsible_idNo

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
titleYes
changedYes
_metricsNo
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the mutation/open-world profile is covered. The description adds only the two required fields, which the schema already states; it says nothing about side effects, whether defaults place the card in a specific lane/column, permission requirements, or duplicate creation risk despite idempotentHint=false.

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 required inputs front-loaded and no wasted wording. It is efficient, though the brevity borders on under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but with 11 parameters at 0% schema coverage and a creation side effect, the definition leaves too much unspecified. An agent cannot tell how to place the card or what the optional IDs refer to.

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% across 11 parameters, so the description must compensate and does not. It names only title and board_id, leaving lane_id, column_id, owner_id, responsible_id, position, due_date, type_id and external_id completely unexplained — notably the overlap between owner_id and responsible_id, and what position means for ordering.

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?

States a specific verb and resource ('Create a Kaiten task/card'), which separates it from update_task or move_task by action alone. It does not explicitly name a sibling or scope, so it falls 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?

The sentence 'Requires title and board_id' implies you need an existing board before creating, which is mildly useful precondition context. There is no explicit when-to-use vs. alternatives (e.g., update_task or move_task) and no guidance on when the optional placement fields matter.

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