mcp-garendesign
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| design_componentA | Analyze user requirements and develop a block-based design strategy. Use this when users ask to 'design component', 'create component', or 'component design'. For complex needs, it breaks down into multiple blocks with step-by-step guidance. |
| query_componentC | Query detailed information of a component including documentation, API, and example code. Provide the component name to get all related information. |
| design_blockB | Design a specific block. This is the second-stage tool in the block-based design strategy for detailed component design. |
| integrate_designC | Combine the overall DesignStrategy with completed blockDesigns and return IntegratedDesign (including props summary, private components used, and composition recommendations). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Component design rules | Rules and constraints for guiding component design |
| Component templates | Standard component file structure templates |
TDQS
Scored across 4 tools
The tools have distinct primary purposes: design_block for detailed block design, design_component for initial strategy and breakdown, integrate_design for combining designs, and query_component for information retrieval. However, design_block and design_component could be confused as both involve design stages, though their descriptions clarify their sequential roles.
All tool names follow a consistent verb_noun pattern with snake_case: design_block, design_component, integrate_design, query_component. This uniformity makes the set predictable and easy to understand.
With 4 tools, this server is well-scoped for its component design domain. Each tool serves a clear role in the design workflow, from strategy to integration and querying, without being overly sparse or bloated.
The tools cover the core design lifecycle: strategy (design_component), detailed design (design_block), integration (integrate_design), and information lookup (query_component). A minor gap is the lack of update or delete operations for designs, but agents can likely work around this given the focused scope.