Skip to main content
Glama

update_task

Modify only the fields you specify on an existing Kanboard task, such as title, description, due date, priority, assignee, or tags. Use it to correct details or reassign work without overwriting other values.

Instructions

Update task fields. Only the fields you pass are changed.

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>"
    },
    "name": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoReplaces all tags
titleNo
task_idYesKanboard task ID
due_dateNo
owner_idNoAssignee user ID; 0 unassigns
priorityNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/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. The description does add genuinely useful semantics beyond annotations: 'Only the fields you pass are changed' tells the agent updates are partial rather than full-replace. It does not mention how to clear a field (the schema's empty-string rule for due_date) or what errors occur on invalid IDs.

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, front-loaded with the operation and followed by the key behavioral constraint. Nothing is wasted, though the brevity leaves the structure thin for a 7-parameter mutation tool.

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, so return values need not be explained. Still, for a 7-parameter write tool with 43% schema coverage, the description should say more about clearing values, assignee semantics, and error behavior to be self-sufficient.

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 43%, so several parameters (title, description) are undocumented anywhere. The description's partial-update statement does help interpret the null defaults as 'leave unchanged,' which is meaningful beyond the schema, but it adds no field-level detail to close the remaining coverage 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+resource ('Update task fields') so the operation is unambiguous. However, it offers no differentiation from close sibling tools such as update_subtask, which an agent would need to choose between for subtask versus task mutations.

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?

No guidance on when to use this versus update_subtask, move_task, reopen_task, or close_task, and no prerequisites or permission notes. The only implicit cue is the partial-update behavior.

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