Kosmodrom

task_create

Creates a task (not a bug) and publishes it right away: with an approver it goes to approval, otherwise to work to the assignee. rulesRevision is the current revision of the workspace's task creation template for the type, and spec is checked against that template; placement is one of featureID / featureKey (product and version from the feature), versionID (no suitable feature) or productID (product backlog). Stage assignees: employee uuid, "any" (any employee) or null (no such stage; the work stage always exists). Returns link, status and available transitions.

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": {
      "title": "<title>",
      "gist": "<gist>",
      "rulesRevision": "<rulesRevision>",
      "type": "<type>"
    },
    "name": "task_create"
  }
}

Input Schema

Name	Required	Description
`ord`	No	Position of the new task, as ord in task edits; omitted - the end of the feature's plan.
`gist`	Yes	Gist: one or two sentences, "problem → solution", up to 300 characters of plain text (no Markdown, links or task keys), in the language of the workspace data.
`spec`	No	Spec (requirements) in the language of the workspace data, per the task creation template; Markdown, HTML is rejected.
`type`	Yes	Work type by the nature of the work; the template depends on it.
`title`	Yes	Task title in the language of the workspace data, up to 200 characters.
`labels`	No	Labels.
`priority`	No	Priority; a human decision, set only at the user's explicit request.
`featureID`	No	Feature ID - the preferred placement
`moduleIDs`	No	Product modules the task affects
`productID`	No	Product ID - the product backlog, last resort
`versionID`	No	Version ID - when no feature fits
`featureKey`	No	Feature key #F12; not with featureID
`componentIDs`	No	Product components the work actually touches; a module does not imply them. May stay empty if unsure
`testAssignee`	No	Tester; default - no testing stage.
`workAssignee`	No	Assignee; default "any".
`workTimePlan`	No	Planned work time in minutes, per the assignee's role level
`rulesRevision`	Yes	Revision of the task creation template for this type; a stale one is rejected
`reviewAssignee`	No	Reviewer; default - no review stage.
`approvalAssignee`	No	Approver; when omitted - the person who asked for the item (set by the server), null - no approval stage.
`workIterationDate`	No	A date within the work iteration, YYYY-MM-DD; defaults to the current iteration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / approvalAssignee / description

Previous value: -"Approver; default - no approval stage."New value: +"Approver; when omitted - the person who asked for the item (set by the server), null - no approval stage."

Changed1 schema field changedNov 1, 2026

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",
+  "marketing",
+  "other",
+  "frontend",
+  "backend",
+  "fullstack",
+  "devops",
+  "tests",
+  "freetest",
+  "smoke",
+  "regression",
+  "testcase"
+]

Changed2 schema fields changedOct 20, 2026

addedInput schema / properties / labels

Added value: +{
+  "description": "Labels.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / priority

Added value: +{
+  "description": "Priority; a human decision, set only at the user's explicit request.",
+  "enum": [
+    "postponed",
+    "unset",
+    "inOrder",
+    "important",
+    "urgent"
+  ],
+  "type": "string"
+}

Changed16 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); default: no approval."New value: +"Approver; default - no approval stage."

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"
+  }
+]

changedInput schema / properties / featureKey / description

Previous value: -"Feature key #F12 (or F12, 12); not with featureID"New value: +"Feature key #F12; not with featureID"

changedInput schema / properties / ord / description

Previous value: -"Position of the new bug; tasks are ordered by `ord` descending. Omitted - end of the feature's plan, so bugs created one by one keep their order."New value: +"Position of the new task, as ord in task edits; omitted - the end of the feature's plan."

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); default: no review."New value: +"Reviewer; default - no review stage."

changedInput schema / properties / spec / description

Previous value: -"Spec (requirements) in the language of the workspace data, per the task creation template. Markdown (HTML is rejected); a write replaces the whole field, including `::: doc` sections and `attach:`, `design:`, `color:` tokens"New value: +"Spec (requirements) in the language of the workspace data, per the task creation template; Markdown, HTML is rejected."

changedInput schema / properties / testAssignee / description

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

changedInput schema / properties / title / description

Previous value: -"Task title in the language of the workspace data, up to 200 characters, conveying the substance of the work rather than an area: \"Authorization\", \"List\", \"Settings\" are poor titles that don't distinguish the task"New value: +"Task title in the language of the workspace data, up to 200 characters."

changedInput schema / properties / type / description

Previous value: -"Type by the nature of the work: planning, analysis, design, research, education, documentation, other - general tasks; frontend, backend, fullstack, devops, tests - development (client and server together - one fullstack task); freetest, smoke, regression, testcase - testing"New value: +"Work type by the nature of the work; the template depends on it."

changedInput schema / properties / workAssignee / description

Previous value: -"Assignee: employee UUID, \"any\" (any employee) or null (no work stage); default \"any\"."New value: +"Assignee; default \"any\"."

addedInput schema / properties / workIterationDate

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

removedInput schema / properties / workIterationKey

Removed value: -{
-  "description": "Iteration key for work outside the current iteration; default - current",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}

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

First observedOct 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false), and the description adds real behavioral context beyond that: immediate publishing, approval vs work routing, stale rulesRevision rejection, and return contents (link, status, transitions). It could go further on failure modes or whether creation is reversible, so a 4 rather than 5.

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?

Dense but front-loaded — creation+publish and routing come first, placement and assignee semantics follow. Every clause carries information, though the single-paragraph packing of many rules slightly hurts scannability.

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 20-parameter mutation with no output schema, the description covers the high-risk decisions (publishing, approval routing, placement precedence, template revision) and summarizes the return value. Undocumented optional params like ord, labels, priority are left to the fully-covered schema, which is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning: placement precedence among featureID/featureKey/versionID/productID, rulesRevision's role as template revision, and stage-assignee conventions ('any'/null, work stage always exists). Modest overlap with schema wording keeps it from a 5.

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?

States a specific verb+resource ('Creates a task') and disambiguates from the sibling bug_create with '(not a bug)', plus discloses the immediate-publish behavior. An agent can distinguish task_create from bug_create and task_publish without opening schemas.

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?

Gives explicit placement decision rules (featureID/featureKey preferred, versionID when no feature fits, productID as last resort) and approval-routing conditions. It doesn't name sibling alternatives like task_publish or task_update to route the agent, so it stops short of a 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

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?