A
license-
qualityB
maintenanceProvides design systems, UI prompts, and layout variation guidance to AI coding tools for generating better user interfaces.
278
1,756
MIT
mcp
Server Details
Provides UX capabilities to enhance the design output and understanding of AI systems.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.1/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
generate_color_scheme and search_icons serve completely distinct purposes: one creates color palettes, the other finds icons. There is no overlap or ambiguity between them.
Naming Consistency5/5
Both tool names follow a clear verb_noun pattern: generate_color_scheme and search_icons. The naming convention is perfectly consistent.
Tool Count3/5
With only two tools, the server feels thin, but the tools cover a specific niche (Material Design assets). The count is borderline, as it's below the typical 3-15 range, but each tool is purposeful.
Completeness4/5
The tools cover the two primary needs for Material Design asset generation: color schemes and icons. Minor gaps exist (e.g., typography, spacing, or other design tokens), but for the apparent scope, the coverage is adequate and workable.
Available Tools
2 toolsgenerate_color_schemeARead-onlyIdempotentInspect
Generates a Material Design color scheme from one or more key colors. Always use this when you need to create a color scheme for an application. The input is one or more named colors in hex format, and the output is a color scheme with a map of color role names to colors in hex format.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| primaryKey | Yes | Required. The primary key color used as the main seed for the scheme. Can be a 6-character hex code (e.g., "#4285F4" or "4285F4"), or any standard CSS color name (e.g., "blue"). | |
| tertiaryKey | No | Optional. The tertiary key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any CSS color name. | |
| secondaryKey | No | Optional. The secondary key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any CSS color name. | |
| backgroundKey | No | Optional. The neutral key color used to generate the color scheme. If omitted, it will be automatically derived from the other keys. Can be a hex code or any CSS color name. | |
| contrastLevel | No | Optional. The contrast level of the color scheme. Values range from -1 (minimum contrast) to 1 (maximum contrast). 0 represents standard contrast (i.e. the design as specified). | |
| optionalTheme | No | Optional. Whether to generate a light or dark theme. If unspecified, and a background key is supplied, it will be inferred from that. If not, it will default to light theme. | |
| optionalSchemeVariant | No | Optional. If only the primary key color is supplied, this will select which variant of the color scheme to use. If only the primary key color is supplied and this is not set, it defaults to "TONAL_SPOT". If multiple key colors are supplied, this is ignored, and it will default to "BRAND". |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| colorScheme | No | The generated color scheme. |
Tool Definition Quality
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the output structure (a map of color role names to hex colors) but does not disclose additional behaviors beyond that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three concise sentences: what it does, when to use it, and what the input/output look like. Every sentence earns its place, and the key information is front-loaded.
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 a rich input schema, annotations, and an output schema, the description appropriately covers purpose, usage context, and high-level input/output. It doesn't need to explain optional parameters or return values because the structured data already does. Minor lack of detail about derivation of optional colors is acceptable.
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%, with each parameter fully documented in the input schema. The description only says 'one or more named colors in hex format,' which is less detailed than the schema and adds no new meaning. Baseline 3 is appropriate because the schema does the heavy lifting.
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 generates a Material Design color scheme from key colors, with a specific verb ('Generates') and resource ('color scheme'). It is easily distinguished from sibling tools (fonts/icons) and adds the input/output shape.
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?
The description explicitly says 'Always use this when you need to create a color scheme for an application,' providing clear when-to-use guidance. There are no alternative tools in the sibling list for this purpose, so no exclusionary guidance is needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_iconsARead-onlyIdempotentInspect
Finds appropriate Material Design icons matching keywords that describe their usage, style, or shape.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | Yes | Required. A list of semantic keywords or metadata tags that describe the desired icon's visual or functional properties. If possible, specify at least three tags to describe usage, style, and shape. Examples: - For a "save" icon: ["save", "diskette", "document", "storage"] - For a "home" icon: ["home", "house", "building"] If multiple tags are provided, the service returns icons that match any part of the tag list, ordered by relevance (number of matching tags). If no tags are provided, all icons are returned. | |
| iconSet | No | Optional. The icon set to search within (e.g., "Material Symbols", "Material Icons"). If omitted, the default icon set of the environment is used. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| icons | No | The names of icons that match the provided tags, ordered by relevance. |
Tool Definition Quality
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds no further behavioral context (e.g., ordering, pagination, or output format), but it does not contradict annotations. This meets the baseline for tools with good annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-formed sentence that immediately conveys the tool's function. It is concise with no redundant information, and the key verb and object are front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple read-only search operation, the presence of a complete input schema (100% coverage) and an output schema, the description provides sufficient context. The purpose is clear, and the schema fills in parameter details, making the tool complete for an agent to invoke correctly.
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 both parameters (tags and iconSet) are thoroughly documented in the schema. The description's mention of 'usage, style, or shape' mildly aligns with the tags parameter but does not add new meaning beyond the rich schema descriptions.
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's purpose: 'Finds appropriate Material Design icons matching keywords that describe their usage, style, or shape.' It specifies the verb (finds), the resource (Material Design icons), and the matching mechanism (keywords), distinguishing it from sibling tools like search_fonts and generate_color_scheme.
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?
The description implies usage through its clear focus on icon search, and the sibling tool names (search_fonts, describe_font) provide context for when to use this tool instead. However, it does not explicitly state 'when not to use' or name alternatives, so it stops short of a perfect score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityDmaintenanceProvides design capabilities including requirement analysis, visual token extraction, design generation, and visual auditing.
- AlicenseCqualityDmaintenanceProvides AI-powered tools to apply UX/UI best practices, Nielsen's heuristics, cognitive biases, and Material-UI patterns to React components. Enables automated application of responsive design, Apple design patterns, and complete UX guidelines through natural language commands.794MIT
- Alicense-qualityBmaintenanceDeploys AI user personas to validate user journeys at scale, surfacing UX friction before real users encounter it.1MIT