Sekura Design MCP

Get migration plan and behavior changes

get_migration_guide

Read-only

Generate a migration guide to upgrade Sekura Design System components from v2 or v3.0 to the current release, including source-specific steps, rollout/rollback guidance, and behavior changes.

Instructions

Upgrade to the current release from v2 or v3.0: full canonical plan, source-specific steps, rollout/rollback guidance, behavior changes, compatibility baseline and optional legacy geometry CSS. componentId filters behavior changes; fromVersion selects the upgrade source while preserving the complete guide.

Input Schema

Name	Required	Description	Default
`componentId`	No
`fromVersion`	No

Output Schema

Name	Required	Description	Default
`changes`	Yes
`version`	Yes
`markdown`	Yes
`componentId`	Yes
`fromVersion`	Yes
`upgradePaths`	No
`compatibility`	Yes
`schemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.2.1Oct 18, 2026

addedInput schema / properties / fromVersion

Added value: +{
+  "enum": [
+    "2.x",
+    "3.0.0",
+    "3.0.x",
+    "3.1.0",
+    "3.1.x"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / changes / items / properties / fromVersions

Added value: +{
+  "items": {
+    "enum": [
+      "2.x",
+      "3.0.0",
+      "3.0.x",
+      "3.1.0",
+      "3.1.x"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / upgradePaths

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "fromVersion": {
+        "enum": [
+          "2.x",
+          "3.0.0",
+          "3.0.x",
+          "3.1.0",
+          "3.1.x"
+        ],
+        "type": "string"
+      },
+      "steps": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "summary": {
+        "type": "string"
+      },
+      "toVersion": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "fromVersion",
+      "toVersion",
+      "summary",
+      "steps"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Addedv3.0.0Oct 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing what the guide contains (canonical plan, source-specific steps, rollout/rollback, compatibility baseline, optional legacy geometry CSS), giving the agent a clear picture of the read-only output it will get.

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?

Two dense sentences, front-loaded with the upgrade scenario and output inventory before addressing parameters. The content list is long but each item is informative and earns its place; minor compression is possible.

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 an output schema present, the description need not explain return values, yet it helpfully summarizes the guide's contents. Both parameters are addressed and the read-only nature is covered by annotations. Complete enough for correct invocation; only explicit alternative-tool routing is missing.

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 description coverage is 0%, so the description must carry the parameter meaning and it largely does: componentId 'filters behavior changes' and fromVersion 'selects the upgrade source while preserving the complete guide'. This clarifies the scope of each parameter's effect, though it could note format/syntax beyond the enum values already in the schema.

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?

The description names a specific verb and resource — it produces a migration/upgrade plan — and enumerates the concrete contents (source-specific steps, rollout/rollback, behavior changes, compatibility baseline). It does not explicitly differentiate itself from the sibling get_behavior, which overlaps on 'behavior changes', so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied by 'Upgrade to the current release from v2 or v3.0', which tells the agent the scenario in which to reach for it. However, there is no explicit when-to-use vs alternative, no mention of when this is the wrong tool versus get_behavior, and no prerequisites.

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