random-design-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_design_descriptionA | Generate one randomized English Markdown frontend design direction. Infer optional productType, audience, and priority context from the user's request and pass those fields in English. Set compatibility to false only when the user explicitly wants unconstrained chaotic combinations. |
| get_versionA | Return the random-design-mcp package version from package.json for debugging cache or publish state. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one generates design descriptions, the other returns a version number. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern using snake_case (generate_design_description, get_version), which is predictable and clear.
With only two tools, the server feels very minimal for its stated purpose of random design generation. While it technically fulfills its core function, the lack of additional tools (e.g., for configuration or output variation) makes it feel incomplete.
The server covers its primary purpose (generating a design description) but lacks any supporting operations like listing past designs, customizing output, or handling multiple generations. The version tool is a minor utility, not core functionality.