Skip to main content
Glama

Kosmodrom

by ai.kosmodrom
OverviewDiscussionsAdmin

feature_update

Destructive

Updates a feature's title, spec, gist, version (moves it), analyst or position (ord) at the user's request; only passed fields change. Changes shared team data; feature status transitions remain a human decision, not available here. Returns the link, product, version, ord, specRevision and changed fields.

Input Schema

NameRequiredDescriptionDefault
keyNoFeature key #F12; not with featureID
ordNoPosition in the version, as drag-and-drop in the web UI; features go by `ord` ascending (tasks the opposite): a value between two neighbours' ord goes between them, below the smallest - first, 0 - end of the version. Neighbours closer than 100 - the version, closed included, is renumbered top down in steps of +10000, the last one at Date.now().
gistNoGist: 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; an empty string clears it.
specNoNew spec in Markdown (no HTML), in the language of the workspace data. Replaces the whole field: existing text, `::: doc` sections and `attach:`, `design:`, `color:` tokens stay only if included.
titleNoNew name
analyticNoNew feature analyst: employee UUID or "any".
featureIDNoFeature ID; not with key
specPatchNoPart 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.
versionIDNoVersion ID to move the feature to.
designUnlinkNotrue - the new spec may drop design markers (`design:`), and designs left unlinked are deleted; otherwise losing a marker is rejected.
expectedSpecRevisionNoThe feature'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.

  1. Changed2 schema fields changed
    • changedInput schema / properties / expectedSpecRevision / description
      Previous value: -"The feature'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 feature'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 / 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"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / analytic
      Added value: +{
+  "description": "New feature analyst: employee UUID or \"any\".",
+  "type": "string"
+}
    • changedInput schema / properties / expectedSpecRevision / description
      Previous value: -"The feature's current specRevision; required when spec changes."New value: +"The feature's current specRevision; required when spec changes. A spec with a revision goes in a separate request, with only gist and designUnlink alongside."
  3. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / key / 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 / key / 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 in the version, as drag-and-drop in the web UI; features go by `ord` ascending (tasks the opposite). Between two neighbours - a value between their ord; first - below the smallest; 0 - end of the version. Neighbours closer than 100 - the whole version, closed included, is renumbered top down from Date.now() - (N - 1) * 10000 in steps of +10000 for N features."New value: +"Position in the version, as drag-and-drop in the web UI; features go by `ord` ascending (tasks the opposite): a value between two neighbours' ord goes between them, below the smallest - first, 0 - end of the version. Neighbours closer than 100 - the version, closed included, is renumbered top down in steps of +10000, the last one at Date.now()."
    • removedInput schema / properties / ord / maximum
      Removed value: -9007199254740991
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

It goes beyond the structured data to provide critical behavioral constraints, such as stating that it 'Changes shared team data' and explicitly detailing the 'only passed fields change' operational behavior.

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?

Although slightly long, the description is highly efficient, front-loading the list of updates and immediately clarifying operational boundaries to prevent misinvocation.

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?

Given the complexity (11 parameters, partial update logic, movement, and spec patching), the description is complete. It covers the 'what' and the 'how' of the update process.

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

Parameters5/5

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

While schema coverage is 100%, the description provides highly specific domain knowledge for complex parameters like 'ord' (position logic) and 'spec' (Markdown replacement rules), adding significant value that cannot be inferred from the JSON schema alone.

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 description provides an exhaustive list of all supported updateable attributes (title, spec, gist, version, analyst, position), making the tool's scope perfectly clear.

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 clearly defines the 'only passed fields change' partial update behavior, distinguishing it from a full replacement. It also explicitly states a limitation: feature status transitions are not handled by this tool.

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

All Kosmodrom toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources