Skip to main content
Glama

create_subtask

Adds a checklist item to an existing Kanboard task, with optional assignee and estimated hours.

Instructions

Add a subtask (checklist item) to a 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>",
      "title": "<title>"
    },
    "name": "create_subtask"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
task_idYesKanboard task ID
user_idNoAssignee user ID
time_estimatedNoHours

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.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 and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: no note on permissions/auth requirements, no statement about what happens if the parent task is missing, and no mention of duplicate checklist items or ordering. Only the 'checklist item' gloss adds any behavioral color.

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?

A single eight-word sentence with the action front-loaded and zero filler. It is tight, though the brevity edges toward under-specification rather than economy of expression.

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 the safety profile, so the description need not explain return values. Still, for a mutation tool on a parent resource it omits prerequisites, failure behavior, and any distinction from update_subtask, leaving it merely adequate.

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 75%, with task_id, user_id and time_estimated documented in the schema; only 'title' is bare but self-evident. The description contributes no additional parameter meaning (e.g., that user_id assigns the checklist item, or that time_estimated is in hours), so it does not compensate for the small gap.

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 ('Add') and resource ('subtask'), and the parenthetical '(checklist item)' usefully disambiguates what a subtask is in this domain. It does not, however, distinguish this from siblings such as update_subtask or create_task, so the agent gets no sibling-level differentiation from the text alone.

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?

The phrase 'to a task' weakly implies this operates on an existing task, but there is no explicit when-to-use guidance, no prerequisite (e.g., the parent task must already exist), and no mention of alternatives like update_subtask for modifying existing checklist items. Guidance is essentially absent.

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