Skip to main content
Glama

update_subtask

Update an existing Kanboard subtask by providing its ID and parent task ID. Modify only the fields you need, such as title, status, or assigned user, while preserving other values.

Instructions

Update an existing Kanboard subtask (partial update). Only the fields you pass are changed; omitted fields keep their current values, and validation runs before any write, so an invalid call modifies nothing. Both 'subtask_id' and 'task_id' are required as identity fields. At least one of title, status, user_id, time_estimated, or time_spent must also be provided. Status: 0 = todo, 1 = in progress, 2 = done. Returns { subtask_id, task_id } on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subtask_idYesID of the subtask to update (required).
task_idYesID of the parent task (required).
titleNoNew subtask title (optional).
statusNoNew status: 0 = todo, 1 = in progress, 2 = done (optional).
user_idNoNew assigned user id (optional).
time_estimatedNoNew estimated time in hours (optional).
time_spentNoNew time spent in hours (optional).
Behavior5/5

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

No annotations provided; description fully covers behavioral traits: partial update (only passed fields change), validation before write (invalid call modifies nothing), required fields, status values, and return type. Comprehensive.

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?

Relatively concise for the information provided. Front-loads purpose and key behavior. Could be slightly more structured but still efficient.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, partial update logic, and no output schema, the description is complete. Explains validation, partial update, requirements, and success return. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: clarifies that both identity fields are required, at least one optional must be provided, status enum meanings, and partial update semantics. Exceeds baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it updates an existing Kanboard subtask (partial update). Distinguishes from siblings like create_subtask, delete_subtask, and other update tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Specifies when to use (update a subtask), clarifies partial update behavior, required identity fields, and that at least one optional field must be provided. Status enumeration is explained. Implicitly excludes creation or deletion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ErnestoCorona/kanboard-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server