Skip to main content
Glama
starwind-ui

Starwind UI MCP Server

by starwind-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

starwind_search

Search Starwind UI v3 styled components, Primitive adapters, and Pro blocks, with results filtered by framework, surface, and plan.

Instructions

Searches Starwind UI v3 styled components, Primitive adapters, and Starwind Pro blocks with framework-aware results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoProject directory used to detect existing Pro setup.
planNo
limitNoPro result limit; defaults to 20 and caps at 50.
queryNo
offsetNo
surfaceNoDefaults to all.
categoryNo
frameworkNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesStructured layered Starwind search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.5.0
    • removedInput schema / properties / category / description
      Removed value: -"Filter Starwind Pro blocks by category."
    • addedInput schema / properties / cwd
      Added value: +{
+  "description": "Project directory used to detect existing Pro setup.",
+  "type": "string"
+}
    • addedInput schema / properties / framework
      Added value: +{
+  "enum": [
+    "astro",
+    "react",
+    "all"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of Pro blocks to return. Defaults to 20, maximum 50."New value: +"Pro result limit; defaults to 20 and caps at 50."
    • removedInput schema / properties / offset / description
      Removed value: -"Offset for paginating Pro block results. Defaults to 0."
    • removedInput schema / properties / plan / description
      Removed value: -"Filter Starwind Pro blocks by plan type."
    • removedInput schema / properties / query / description
      Removed value: -"Search query for components and Pro blocks."
    • addedInput schema / properties / surface
      Added value: +{
+  "description": "Defaults to all.",
+  "enum": [
+    "styled",
+    "primitive",
+    "all"
+  ],
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {
+      "additionalProperties": {},
+      "description": "Structured layered Starwind search result.",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  2. Addedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description bears full burden for behavioral disclosure. It only states what the tool searches but does not confirm it's read-only, describe side effects, authentication needs, rate limits, or any other behavioral characteristics.

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 is a single, front-loaded sentence that efficiently conveys the tool's action and scope. It could be slightly improved by structuring with lists or brief usage notes, but it is not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, many without descriptions), the description is insufficient. It does not mention filtering dimensions like surface, category, plan, or how the output is structured, despite the output schema existing. The agent would lack context to leverage all features.

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

Parameters2/5

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

Schema description coverage is low at 38% (3 of 8 parameters have descriptions). The tool description adds no parameter-level meaning beyond the schema's sparse descriptions. It does not explain the role of query, category, offset, plan, or framework in search behavior.

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 clearly states the tool searches across specific resources (Starwind UI v3 styled components, Primitive adapters, Starwind Pro blocks) with framework-aware results. This distinguishes it from sibling tools (init, add, docs, migrate) which are not search functions.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or exclusions. The context is purely implicit from the tool name and siblings.

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

Deploy Server

Other Tools