Skip to main content
Glama

update_task

Destructive

Modify card fields such as title, description, due date, owner, and condition via PATCH. Use it to edit existing tasks; move tasks between columns with move_task instead.

Instructions

Update card fields via PATCH. condition: 1=live, 2=archived, 3=deleted. Workflow status (queued/in-progress/done) comes from the column — use move_task. Responsible is set only on create_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": {
      "card_id": "<card_id>"
    },
    "name": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
card_idYes
type_idNo
due_dateNo
owner_idNo
conditionNo
propertiesNo
descriptionNo
external_idNo

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
titleYes
changedYes
_metricsNo
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent writes, but the description adds real context beyond them: it discloses PATCH semantics (partial field update), and supplies the otherwise missing meaning of the condition codes, including that 3 equals deleted — which is what makes the destructive hint concrete. It does not cover permissions, reversibility, or whether omitted fields are preserved.

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?

Three short sentences, front-loaded with the core action, then enum semantics, then sibling routing. No filler, though the telegraphic 'condition: 1=live...' fragment reads slightly like notes rather than prose.

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?

Output schema exists so return values need not be explained, and the mutation's most dangerous parameter is decoded. However, for a destructive, non-idempotent 9-parameter write tool, the definition says nothing about required scope/auth, whether condition=3 is a soft or hard delete, or partial-update behavior for omitted fields.

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 0% across 9 parameters, so the description carries the burden. It usefully defines 'condition' (1/2/3) and rules out status and responsible, but leaves title, type_id, due_date, properties, description, external_id, and the relation of owner_id to 'Responsible' undocumented — the latter creates mild ambiguity since owner_id exists in the schema.

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 ('Update card fields via PATCH') and names the sibling tools it is not (move_task, create_task). The only weakness is calling the resource 'card fields' while the tool is named update_task and siblings use task terminology, though the underlying API mapping is implied.

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?

Explicitly carves out two neighboring capabilities with their replacements: workflow status 'comes from the column — use move_task' and 'Responsible is set only on create_task.' An agent knows both what this tool cannot do and which sibling to call instead.

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