Skip to main content
Glama
azimov777

Casefile

by azimov777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Change task status

transition

Move a task to a new status along the fixed workflow table, enforcing rules like assignee, summary, and blockers before allowing the change.

Instructions

Moves a task to another status along the fixed transition table.

Refusals: leaving in_progress without a summary filed since the last entry into it — summary_required; entering in_progress without an assignee — assignee_required, by anyone but the assignee — assignee_mismatch (assignee and caller signature in details), with an open blocker — task_blocked, with an unanswered blocking question — task_has_open_blocking_questions (question numbers in details.questions); open with incomplete sections — task_sections_incomplete; cancelled with open children — task_has_unclosed_children; done — closing_not_a_transition, since a task is closed by close_task; a move outside the table — transition_not_allowed, the allowed targets in details.allowed.

A task waiting in open stays there when its carrier closes: neither an answer nor a closed blocker moves it, and it becomes a candidate again with no status_changed entry. Each entry into in_progress starts a new pass of the task.

cancelled takes no verdicts. It clears the blocked feature of the tasks this one blocked (blocks), with no entry in their cases.

The response names the new status and version and the number of the filed status_changed entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesTarget status
keyYesTask 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`
reasonNoWhy the task moves. Required for any step back along `backlog < open < in_progress < done` and for `cancelled` (`transition_reason_required` otherwise), optional elsewhere. Filed in the `status_changed` entry as text only: a wait is held by its carrier, an open `blocking` question or `blocked_by`, and not by the reason

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
statusYesTask status
entriesYesNumbers 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
versionYesTask version after the call
parent_entryNoNumber 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.

  1. Changed3 schema fields changedv0.10.1
    • changedInput schema / properties / reason / description
      Previous value: -"Why the task moves. Required for any step back along `backlog < open < in_progress < done`, for `cancelled` and for `waiting` (`transition_reason_required` otherwise), optional elsewhere. For `waiting` it is the only record of what the task waits for. Filed in the `status_changed` entry"New value: +"Why the task moves. Required for any step back along `backlog < open < in_progress < done` and for `cancelled` (`transition_reason_required` otherwise), optional elsewhere. Filed in the `status_changed` entry as text only: a wait is held by its carrier, an open `blocking` question or `blocked_by`, and not by the reason"
    • changedInput schema / properties / to / enum
      Previous value: -[
-  "backlog",
-  "open",
-  "in_progress",
-  "waiting",
-  "done",
-  "cancelled"
-]New value: +[
+  "backlog",
+  "open",
+  "in_progress",
+  "done",
+  "cancelled"
+]
    • changedOutput schema / properties / status / enum
      Previous value: -[
-  "backlog",
-  "open",
-  "in_progress",
-  "waiting",
-  "done",
-  "cancelled"
-]New value: +[
+  "backlog",
+  "open",
+  "in_progress",
+  "done",
+  "cancelled"
+]
  2. Changed18 schema fields changedv0.5.2
    • removedInput schema / $defs
      Removed value: -{
-  "TaskStatus": {
-    "description": "Зашитый список статусов (`CONCEPT.md`, 3.3).",
-    "enum": [
-      "backlog",
-      "open",
-      "in_progress",
-      "waiting",
-      "done",
-      "cancelled"
-    ],
-    "title": "TaskStatus",
-    "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 / reason / description
      Previous value: -"Почему задача идёт туда. Обязательна для любого шага назад по цепочке `backlog < open < in_progress < done`, для `cancelled` и для `waiting`; в остальных переходах необязательна. У `waiting` она называет, чего ждём, — больше это записать негде. Попадает в дело записью `status_changed`"New value: +"Why the task moves. Required for any step back along `backlog < open < in_progress < done`, for `cancelled` and for `waiting` (`transition_reason_required` otherwise), optional elsewhere. For `waiting` it is the only record of what the task waits for. Filed in the `status_changed` entry"
    • removedInput schema / properties / reason / examples
      Removed value: -[
-  "Жду ответа на TRK-42#7"
-]
    • removedInput schema / properties / to / $ref
      Removed value: -"#/$defs/TaskStatus"
    • changedInput schema / properties / to / description
      Previous value: -"Целевой статус"New value: +"Target status"
    • addedInput schema / properties / to / enum
      Added value: +[
+  "backlog",
+  "open",
+  "in_progress",
+  "waiting",
+  "done",
+  "cancelled"
+]
    • removedInput schema / properties / to / examples
      Removed value: -[
-  "open"
-]
    • addedInput schema / properties / to / type
      Added value: +"string"
    • 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"
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover the safety profile (not read-only, not idempotent, not destructive, closed-world); the description goes far beyond them, disclosing named refusal codes with detail payloads, the side effect that `cancelled` clears the `blocked` feature of blocked tasks with no case entry, and the re-entry/pass semantics of `in_progress`.

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?

The core action is front-loaded in one sentence, and the remaining prose is dense but load-bearing (refusal codes, side effects, open-task semantics). The refusal enumeration is long, but each entry carries distinct information an agent needs.

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?

For a state-machine transition with a fixed table, the description covers preconditions, refusal reasons, side effects, and edge-case semantics (tasks waiting in `open`), and an output schema already covers the return shape. Nothing material is missing.

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 100%, so `key`, `to`, and `reason` are already fully documented in the schema, including the `reason`-required cases. The description adds no parameter-level detail beyond that, 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 plus the mechanism ('moves a task to another status along the fixed transition table'), and explicitly routes the `done` case to the sibling `close_task`. It does not, however, differentiate itself from `move_task`, which an agent could easily confuse with a status change.

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?

The refusal catalogue effectively defines when the tool will and will not succeed, and `close_task` is named as the correct alternative for closing. What's missing is a positive statement of when to reach for `transition` versus `update_task` or `move_task`.

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

Deploy Server

Other Tools