Casefile

Overview Schema Source Related Servers Discussions Admin

Update task

update_task

Idempotent

Edit selected Casefile task fields—title, description, checks, assignee, priority, decisions—while omitted values stay unchanged. Use it for status-aware task updates with version checks.

Instructions

Changes the given fields of a task; fields left out stay as they are.

Title, description and sections are fixed from open on. A task past backlog has them edited by a return to backlog through transition with a reason, this call, and a move forward again to open and in_progress.

Each changed field files section_changed or field_changed, an assignee change files assignee_changed. An edit of one check names its number, and the earlier verdicts on that check become outdated.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	Task key `PROJECT-N`, case-insensitive; a previous key of a moved task addresses it as well. An unknown key is refused with `task_not_found`
`changes`	Yes
`version`	No	Task version read earlier. When given and the task has changed since, the call is refused with `version_conflict` instead of overwriting the other change; when left out, the edit applies on top of the current version

Output Schema

TableJSON Schema

Name	Required	Description
`key`	Yes
`status`	Yes	Task status
`entries`	Yes	Numbers of the entries filed in this task's case, in filing order. Empty when the sent values were already in place; the version then stays the same
`version`	Yes	Task version after the call
`parent_entry`	No	Number of the `link_added` entry filed into the parent task's own case when `create_task` was given `parent`. `null` when no `parent` was given, and always `null` for `transition` and `update_task`: they touch no other task's case.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.10.1Oct 6, 2026

addedInput schema / $defs / TaskChanges / properties / decisions

Added value: +{
+  "description": "The whole new list, editable in any status but `done` and `cancelled`. References `PROJECT#N` to `decision` entries of a project's case, up to 20: the project decisions the task relies on. A task entry such as `TRK-42#7` is refused with `task_fields_invalid` (`task_entry`), a project entry of another type with `not_a_decision`. A reference not yet in the field leads to a decision in force; a superseded one is refused with `decision_not_in_force`, its successor in `details`. A reference already in the field stays there after its decision is superseded",
+  "examples": [
+    [
+      "TRK#15"
+    ]
+  ],
+  "items": {
+    "type": "string"
+  },
+  "title": "Decisions",
+  "type": "array"
+}

changedOutput schema / properties / status / enum

Previous value: -[
-  "backlog",
-  "open",
-  "in_progress",
-  "waiting",
-  "done",
-  "cancelled"
-]New value: +[
+  "backlog",
+  "open",
+  "in_progress",
+  "done",
+  "cancelled"
+]

Changed34 schema fields changedv0.5.2Sep 25, 2026

changedInput schema / $defs / CheckEditArg / description

Previous value: -"Правка одной проверки: её номер и новый текст."New value: +"Rewrite of one check: its number and new text."

changedInput schema / $defs / CheckEditArg / properties / no / description

Previous value: -"Номер проверки в нынешнем списке задачи, с 1"New value: +"Number of the check in the current list, from 1"

removedInput schema / $defs / CheckEditArg / properties / no / examples
```
Removed value: -[
-  3
-]
```

changedInput schema / $defs / CheckEditArg / properties / text / description

Previous value: -"Новая формулировка этой проверки; остальные остаются теми же байтами"New value: +"New wording of this check"

removedInput schema / $defs / CheckEditArg / properties / text / examples

Removed value: -[
-  "`docker compose run --rm test` зелёный целиком"
-]

changedInput schema / $defs / TaskChanges / description

Previous value: -"Что поменять в задаче. Непереданное поле не трогается.\n\nСтатуса здесь нет — он меняется `transition`; ключа нет — он неизменяем. У\n`assignee` осмыслен `null`: он снимает исполнителя. У остальных полей `null` смысла\nне имеет, и схема его не пропустит."New value: +"Fields to change; a field left out stays as it is. Title, description, sections\nand checks are editable only in `backlog`; elsewhere they are refused with\n`task_field_locked`."

changedInput schema / $defs / TaskChanges / properties / assignee / description

Previous value: -"Имя участника или метка временного агента; `null` снимает исполнителя"New value: +"Participant name or temporary agent label; `null` clears it. The name is compared with the caller's signature regardless of case, and every session signed with that name counts as the assignee. Replacing another participant's name takes the task over from them: the tracker accepts it, files `assignee_changed` and informs no one"

removedInput schema / $defs / TaskChanges / properties / assignee / examples
```
Removed value: -[
-  "release_bot"
-]
```

changedInput schema / $defs / TaskChanges / properties / check / description

Previous value: -"Переписывает одну проверку на месте, не трогая остальные; только в `backlog`. Главный способ правки: переписывают обычно одну — «эту проверку выполнить нельзя», — а состав меняют редко. Вместе с `checks` не принимается: это два разных ответа на один вопрос"New value: +"Rewrites one check in place; the other checks stay byte for byte, and the `section_changed` entry names the check number. Refused together with `checks` (`task_fields_invalid`)"

changedInput schema / $defs / TaskChanges / properties / checks / description

Previous value: -"Обзорные проверки целиком, списком; только в `backlog`. Этим меняют **состав**: добавляют проверку, снимают, переставляют. Переписать одну — `check`: пересылка восьми строк ради третьей пропускает опечатку в остальных семи молча"New value: +"All review checks as a list: changes their composition — a check added, removed or moved"

changedInput schema / $defs / TaskChanges / properties / constraints / description

Previous value: -"Раздел «ограничения»; только в `backlog`"New value: +"Section `constraints`"

changedInput schema / $defs / TaskChanges / properties / context / description

Previous value: -"Раздел «контекст»; только в `backlog`"New value: +"Section `context`"

changedInput schema / $defs / TaskChanges / properties / description / description

Previous value: -"Описание задачи; только в `backlog`"New value: +"Task description"

changedInput schema / $defs / TaskChanges / properties / goal / description

Previous value: -"Раздел «цель»; только в `backlog`"New value: +"Section `goal`"

changedInput schema / $defs / TaskChanges / properties / output / description

Previous value: -"Раздел «выход»; только в `backlog`"New value: +"Section `output`"

removedInput schema / $defs / TaskChanges / properties / priority / $ref
```
Removed value: -"#/$defs/TaskPriority"
```
changedInput schema / $defs / TaskChanges / properties / priority / description
```
Previous value: -"Приоритет"New value: +"Task priority"
```
addedInput schema / $defs / TaskChanges / properties / priority / enum
```
Added value: +[
+  "low",
+  "normal",
+  "high",
+  "critical"
+]
```
removedInput schema / $defs / TaskChanges / properties / priority / examples
```
Removed value: -[
-  "high"
-]
```
addedInput schema / $defs / TaskChanges / properties / priority / type
```
Added value: +"string"
```

changedInput schema / $defs / TaskChanges / properties / title / description

Previous value: -"Название задачи; только в `backlog`"New value: +"Task title"

removedInput schema / $defs / TaskPriority

Removed value: -{
-  "description": "Приоритет. Порядок членов — от низшего к высшему, на него опирается сортировка поиска.",
-  "enum": [
-    "low",
-    "normal",
-    "high",
-    "critical"
-  ],
-  "title": "TaskPriority",
-  "type": "string"
-}

changedInput schema / properties / key / description

Previous value: -"Ключ задачи, например `TRK-42`. Регистр не важен"New value: +"Task key `PROJECT-N`, case-insensitive; a previous key of a moved task addresses it as well. An unknown key is refused with `task_not_found`"

changedInput schema / properties / version / description

Previous value: -"Версия задачи, прочитанная раньше. Присланная обратно, она превращает потерянное чужое изменение в отказ `version_conflict` вместо тихой перезаписи; не передана — правка ложится поверх текущей версии"New value: +"Task version read earlier. When given and the task has changed since, the call is refused with `version_conflict` instead of overwriting the other change; when left out, the edit applies on top of the current version"

removedInput schema / properties / version / examples
```
Removed value: -[
-  3
-]
```

removedOutput schema / $defs

Removed value: -{
-  "TaskStatus": {
-    "description": "Зашитый список статусов (`CONCEPT.md`, 3.3).",
-    "enum": [
-      "backlog",
-      "open",
-      "in_progress",
-      "waiting",
-      "done",
-      "cancelled"
-    ],
-    "title": "TaskStatus",
-    "type": "string"
-  }
-}

changedOutput schema / description

Previous value: -"Ответ изменяющего инструмента: что стало и чем это подшито, без карточки."New value: +"Task state after the call and the entries it filed; the card in full is returned\nby `get_task`."

addedOutput schema / properties / entries / description

Added value: +"Numbers of the entries filed in this task's case, in filing order. Empty when the sent values were already in place; the version then stays the same"

addedOutput schema / properties / parent_entry

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Number of the `link_added` entry filed into the parent task's own case when `create_task` was given `parent`. `null` when no `parent` was given, and always `null` for `transition` and `update_task`: they touch no other task's case.",
+  "title": "Parent Entry"
+}

removedOutput schema / properties / status / $ref
```
Removed value: -"#/$defs/TaskStatus"
```
addedOutput schema / properties / status / description
```
Added value: +"Task status"
```

addedOutput schema / properties / status / enum

Added value: +[
+  "backlog",
+  "open",
+  "in_progress",
+  "waiting",
+  "done",
+  "cancelled"
+]

addedOutput schema / properties / status / type
```
Added value: +"string"
```
addedOutput schema / properties / version / description
```
Added value: +"Task version after the call"
```

First observedSep 23, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well past the annotations (readOnly=false, idempotent=true, destructive=false) by disclosing side effects: which journal entries get filed (section_changed, field_changed, assignee_changed), that editing one check marks earlier verdicts outdated, and that taking over another participant's assignee notifies no one. This is exactly the behavioral context annotations cannot carry.

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?

Front-loads the core semantic in the first sentence, then adds constraint and side-effect detail in two short paragraphs. Every sentence carries information, though the editability rule is stated twice (description body and schema).

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

Completeness4/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 return values need not be described. The description fills in the lock/unlock workflow and journal side effects; only version/optimistic-concurrency behavior is left entirely to the schema.

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 coverage is 67% and the nested TaskChanges definitions are already richly annotated (field-level editability, refusal codes, null-clears-assignee). The description restates the partial-update rule already present in the schema rather than adding new per-parameter meaning, so the baseline 3 applies.

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 ('Changes the given fields of a task') and immediately adds the partial-update semantics that distinguish it from a full replace. It does not name a sibling like transition or move_task explicitly, but the scope is unambiguous.

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

Usage Guidelines4/5

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

Explains the editability window ('Title, description and sections are fixed from `open` on') and routes the agent to `transition` as the way to unlock a locked task. That is real when-to-use guidance, though it stops short of explicit when-not-to-use this versus move_task/transition for status work.

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