Skip to main content
Glama

Kosmodrom

by ai.kosmodrom
OverviewDiscussionsAdmin

feature_spec_sync

Read-only

Returns the context for updating a feature's spec from its tasks: feature.spec, tasks[].spec and tasks[].result in one batch plus the workspace's spec-update guidelines (instructions); writes nothing. includeTaskIDs adds full contexts with chats of tasks with discrepancies. mode=analyze - differences and a full new version without saving; mode=apply - when the user asks to apply the update.

Input Schema

NameRequiredDescriptionDefault
keyNoFeature key #F12; not with featureID
modeYesanalyze - propose without saving; apply - the user asks to apply
basisNoactual (default) - actual state from the tasks; requirements - confirmed in chats
chatLimitNoLatest messages per full context, 1-100; older ones are read from the chat with a before cursor.
featureIDNoFeature ID; not with key
taskTypesNoTask and bug types to include; default frontend, backend, fullstack, design
includeTaskIDsNoTasks with discrepancies to add with full context and chat, up to 20; requires taskTypes, the same as in the previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / chatLimit / description
      Previous value: -"Latest messages per full context, 1-100; older via chat.before"New value: +"Latest messages per full context, 1-100; older ones are read from the chat with a before cursor."
    • 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"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'writes nothing' — important because an 'apply' mode would otherwise read as a mutation. It also discloses that includeTaskIDs pulls full contexts with chats and that older chat messages are read via a cursor, which annotations do not cover.

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 purpose is front-loaded in the first clause and the text is information-dense with no filler. It is a single run-on block of semicolon-separated clauses, which costs some readability, but almost every clause carries distinct content.

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?

With 7 parameters at full schema coverage, a read-only profile already defined by annotations, and no output schema, the description supplies what is missing: return contents, the no-write guarantee, and mode semantics. Only the sibling-vs-sibling routing (task_spec_sync) is left implicit.

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 the baseline is 3. The description largely restates the schema's own wording for mode and includeTaskIDs ('full contexts with chats of tasks with discrepancies') rather than adding new format or interaction detail; basis and chatLimit get no description-side elaboration.

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?

Specific verb and resource: it 'Returns the context for updating a feature's spec from its tasks' and enumerates exactly what comes back (feature.spec, tasks[].spec, tasks[].result, guidelines). The phrase 'writes nothing' pins down the operation type and separates it from task_spec_sync and feature_update.

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?

Mode selection is spelled out: 'mode=analyze - differences and a full new version without saving; mode=apply - when the user asks to apply the update.' This gives a clear trigger for each mode, though it never names the obvious alternative (task_spec_sync) or states when not to reach for 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