Skip to main content
Glama

update_subtask

Update a Kanboard subtask's title or status (todo, in_progress, done) by providing the task ID and subtask ID.

Instructions

Change a subtask's status or title.

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": {
      "subtask_id": "<subtask_id>",
      "task_id": "<task_id>"
    },
    "name": "update_subtask"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
statusNo
task_idYesKanboard task ID
subtask_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/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 description owes context beyond that and delivers none. It never says whether this is a partial update (both fields default to null), whether omitting a field leaves it untouched, or whether a status change has side effects on the parent task. Naming the mutable fields mostly repeats what the schema shows.

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 short sentence with no filler and the scope stated up front. It is efficient, though the brevity borders on under-specification rather than economy.

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?

For a four-parameter mutation tool with low schema documentation, the definition is too thin. An output schema exists so return values need no explanation, but the missing partial-update semantics, required-field roles (task_id plus subtask_id) and side effects leave real ambiguity about how to invoke it correctly.

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 coverage is only 25% (only task_id is documented), so the description must compensate and largely does not. It implies title and status are the updatable values but explains nothing about the null defaults (is null 'no change' or 'clear the value'?) or the relationship between subtask_id and task_id. The status enum is only visible in the schema, not the description.

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 names a specific verb ('Change') and resource ('a subtask'), plus the two updatable fields, so an agent can separate it from create_subtask or update_task by the resource noun alone. It stops short of explicitly contrasting those siblings, which keeps it from 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 Guidelines2/5

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

There is no when-to-use guidance, no statement of prerequisites (permissions, existing subtask), and no routing to alternatives such as update_task when the target is a top-level task rather than a subtask. The agent must infer all of this from the tool name.

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