Kosmodrom

task_update

Destructive

Edits a task or bug (shared team data); only the passed fields change: title, spec, gist, result, priority, labels, placement (featureID or featureKey, featureID null removes it from the feature; versionID; productID), work iteration, bug fields (build, bugType, stage, browser, devices, fuzzy), type within its kind, modules and components (full new lists), stage assignees and ord. Stage assignees: employee uuid, "any" (any employee) or null (no such stage; the work stage always exists). Status is not changed here; returns link, status, specRevision and changed.

Input Schema

Name	Required	Description
`ID`	No	Task ID; preferred over key.
`key`	No	Task number, if the ID is unknown.
`ord`	No	Position in lists, as drag-and-drop in the web UI; tasks go by ord descending (a feature's tasks follow its plan top down): a value between two neighbours' ord goes between them, above the largest - on top, 0 - last. When neighbours are under 100 apart, the feature's tasks, closed included, are renumbered top down from Date.now() in steps of -10000.
`gist`	No	Gist: one or two plain-text sentences "problem → solution", up to 300 characters, without Markdown, links or task keys, in the language of the workspace data; an empty string clears it.
`spec`	No	New spec (requirements): Markdown in the language of the workspace data, HTML is rejected. Replaces the whole field - text, `::: doc` sections and `attach:`, `design:`, `color:` tokens left out are removed.
`type`	No	New type: the work type for a task, the criticality for a bug; a task does not become a bug or back.
`build`	No	Build where the defect was reproduced (bugs only).
`fuzzy`	No	Intermittent bug: does not reproduce every time (bugs only).
`stage`	No	Stand where the bug was reproduced: dev - development and autotests, alpha - manual QA, prod - production data.
`title`	No	New name
`labels`	No	Labels; an empty array removes all.
`result`	No	Report on the work done: Markdown in the language of the workspace data, HTML is rejected; replaces the whole field, like spec.
`browser`	No	Browser where the bug was reproduced (bugs only).
`bugType`	No	Defect nature (bugs only): ui - interface, fn - functionality, ux - usability, spec - documentation; not the severity, which is type.
`devices`	No	IDs of devices from the company's QA devices where the bug was reproduced; an unknown ID is rejected. Bugs only; full new list, [] clears it.
`priority`	No	Priority; a human decision, set only at the user's explicit request.
`featureID`	No	Feature to move the task to; null removes it from its feature.
`moduleIDs`	No	Full new list of module IDs, replacing the current one; [] removes all.
`productID`	No	Product to move the task to; it lands in the product's current development version.
`specPatch`	No	Part of the spec, ops in order: replace / insertBefore / insertAfter / delete a section by heading ("## Chat"; text - whole section), append, find an exact unique fragment → replace. With expectedSpecRevision.
`versionID`	No	Version to move the task to when no feature fits.
`featureKey`	No	Key of the feature to move the task to (#F12), instead of featureID.
`resultPatch`	No	Like specPatch, for result except QA notes; apart from spec.
`componentIDs`	No	Full new list of the actually affected component IDs, replacing the current one; [] removes all, adding means the current ones plus new.
`designUnlink`	No	true lets a spec / result write drop design markers (designs left unlinked are deleted); otherwise it is rejected.
`testAssignee`	No	Tester; a bug always keeps its testing stage, null is rejected.
`workAssignee`	No	Assignee.
`workTimePlan`	No	Planned work time in minutes, per the assignee's role level
`reviewAssignee`	No	Reviewer.
`approvalAssignee`	No	Approver.
`workIterationDate`	No	A date within the work iteration, YYYY-MM-DD; moves the work to that iteration.
`expectedSpecRevision`	No	The task's current specRevision; required when spec or specPatch changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 24, 2026

changedInput schema / properties / designUnlink / description

Previous value: -"true lets a spec / result write drop design markers (designs left without links are deleted); otherwise losing a marker is rejected."New value: +"true lets a spec / result write drop design markers (designs left unlinked are deleted); otherwise it is rejected."

changedInput schema / properties / expectedSpecRevision / description

Previous value: -"The task's current specRevision; required when spec changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside."New value: +"The task's current specRevision; required when spec or specPatch changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside."

addedInput schema / properties / resultPatch

Added value: +{
+  "description": "Like specPatch, for result except QA notes; apart from spec.",
+  "items": {
+    "properties": {
+      "find": {
+        "maxLength": 200000,
+        "type": "string"
+      },
+      "heading": {
+        "maxLength": 300,
+        "type": "string"
+      },
+      "op": {
+        "enum": [
+          "replace",
+          "insertBefore",
+          "insertAfter",
+          "delete",
+          "append",
+          "find"
+        ],
+        "type": "string"
+      },
+      "replace": {
+        "maxLength": 200000,
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 200000,
+        "type": "string"
+      }
+    },
+    "required": [
+      "op"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / specPatch

Added value: +{
+  "description": "Part of the spec, ops in order: replace / insertBefore / insertAfter / delete a section by heading (\"## Chat\"; text - whole section), append, find an exact unique fragment → replace. With expectedSpecRevision.",
+  "items": {
+    "properties": {
+      "find": {
+        "maxLength": 200000,
+        "type": "string"
+      },
+      "heading": {
+        "maxLength": 300,
+        "type": "string"
+      },
+      "op": {
+        "enum": [
+          "replace",
+          "insertBefore",
+          "insertAfter",
+          "delete",
+          "append",
+          "find"
+        ],
+        "type": "string"
+      },
+      "replace": {
+        "maxLength": 200000,
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 200000,
+        "type": "string"
+      }
+    },
+    "required": [
+      "op"
+    ],
+    "type": "object"
+  },
+  "minItems": 1,
+  "type": "array"
+}

Changed7 schema fields changedOct 20, 2026

changedInput schema / properties / expectedSpecRevision / description

Previous value: -"The task's current specRevision; required when spec changes."New value: +"The task's current specRevision; required when spec changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside."

addedInput schema / properties / fuzzy

Added value: +{
+  "description": "Intermittent bug: does not reproduce every time (bugs only).",
+  "type": "boolean"
+}

addedInput schema / properties / productID

Added value: +{
+  "description": "Product to move the task to; it lands in the product's current development version.",
+  "format": "uuid",
+  "type": "string"
+}

changedInput schema / properties / testAssignee / description

Previous value: -"Tester."New value: +"Tester; a bug always keeps its testing stage, null is rejected."

changedInput schema / properties / type / description

Previous value: -"New work type (non-bugs only)."New value: +"New type: the work type for a task, the criticality for a bug; a task does not become a bug or back."

changedInput schema / properties / type / enum

Previous value: -[
-  "planning",
-  "analysis",
-  "design",
-  "documentation",
-  "research",
-  "education",
-  "other",
-  "frontend",
-  "backend",
-  "fullstack",
-  "devops",
-  "tests",
-  "freetest",
-  "smoke",
-  "regression",
-  "testcase"
-]New value: +[
+  "planning",
+  "analysis",
+  "design",
+  "documentation",
+  "research",
+  "education",
+  "other",
+  "frontend",
+  "backend",
+  "fullstack",
+  "devops",
+  "tests",
+  "freetest",
+  "smoke",
+  "regression",
+  "testcase",
+  "bug_trivial",
+  "bug_minor",
+  "bug_major",
+  "bug_critical",
+  "bug_block"
+]

addedInput schema / properties / workIterationDate

Added value: +{
+  "description": "A date within the work iteration, YYYY-MM-DD; moves the work to that iteration.",
+  "type": "string"
+}

Changed12 schema fields changedOct 8, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / approvalAssignee / description

Previous value: -"Approver: employee uuid, \"any\" (any employee) or null (no approval stage)."New value: +"Approver."

changedInput schema / properties / devices / description

Previous value: -"IDs of devices from the company's QA devices: for a bug - where reproduced, for a task - where to test and where tested. Full new list; [] clears it."New value: +"IDs of devices from the company's QA devices where the bug was reproduced; an unknown ID is rejected. Bugs only; full new list, [] clears it."

changedInput schema / properties / featureKey / anyOf

Previous value: -[
-  {
-    "maxLength": 12,
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "exclusiveMinimum": 0,
-    "maximum": 9007199254740991,
-    "type": "integer"
-  }
-]New value: +[
+  {
+    "maxLength": 12,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  }
+]

removedInput schema / properties / key / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / key / minimum
```
Removed value: --9007199254740991
```

changedInput schema / properties / ord / description

Previous value: -"Position in lists, as drag-and-drop in the web UI. Tasks are sorted by ord DESCENDING (a feature's tasks follow its plan top down): a value between two neighbors' ord goes between them, above the largest - on top, 0 - last (the server assigns it). When neighbors are under 100 apart or the user asks for a re-sort, all of the feature's tasks including closed ones are renumbered: Date.now() for the top one, then steps of -10000."New value: +"Position in lists, as drag-and-drop in the web UI; tasks go by ord descending (a feature's tasks follow its plan top down): a value between two neighbours' ord goes between them, above the largest - on top, 0 - last. When neighbours are under 100 apart, the feature's tasks, closed included, are renumbered top down from Date.now() in steps of -10000."

removedInput schema / properties / ord / maximum
```
Removed value: -9007199254740991
```

changedInput schema / properties / reviewAssignee / description

Previous value: -"Reviewer: employee uuid, \"any\" (any employee) or null (no review stage)."New value: +"Reviewer."

changedInput schema / properties / testAssignee / description

Previous value: -"Tester: employee uuid, \"any\" (any employee) or null (no testing stage)."New value: +"Tester."

changedInput schema / properties / workAssignee / description

Previous value: -"Assignee: employee uuid or \"any\" (any employee); null is not allowed - the work stage always exists."New value: +"Assignee."

changedInput schema / properties / workTimePlan / anyOf

Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / devices

Added value: +{
+  "description": "IDs of devices from the company's QA devices: for a bug - where reproduced, for a task - where to test and where tested. Full new list; [] clears it.",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "type": "array"
+}

First observedOct 6, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond readOnly=false and destructive=true, it discloses full-field replacement and token deletion for spec/result, null-removal behavior for featureID, rejection of unknown device IDs, and the returned fields. These are exactly the destructive side effects an agent needs before invoking a mutation.

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 description front-loads purpose and key invariants and, given 32 parameters, remains dense with little filler. However, it is a single semicolon-heavy paragraph that would be easier to scan as structured groups, so it is not a 5.

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?

For a 32-parameter mutation with no output schema, it covers the important behavioral gotchas and states the return fields, while annotations cover safety. Some operational details such as permissions, atomicity, and all parameter interactions are left to the rich schema, so it is strong but not exhaustive.

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 100%, so the schema already documents all 32 parameters in detail; the description mainly summarizes parameter groups rather than adding syntax or constraints beyond it. It does reinforce 'only the passed fields change' and some relationships, but that is baseline-level value for a fully documented schema.

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?

The opening 'Edits a task or bug' gives a precise verb and resource, and 'only the passed fields change' states the partial-update model. It also rules out status changes, so an agent can distinguish it from status-changing siblings such as task_done/task_take without opening another schema.

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?

It explains when to use it for field-level edits and gives exclusions such as 'Status is not changed here' and priority being set only at explicit user request. It also notes that a spec with a revision must go in a separate request, but it does not name the sibling tools to use for the excluded operations, so it is not a full 5.

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

All Kosmodrom tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?