Skip to main content
Glama
lnksoul1

UI Design MCP Server

by lnksoul1

Generate Gradient

ui_generate_gradient
Read-onlyIdempotent

Generate CSS gradients from a base color with automatic color stops, supporting linear and radial types plus color harmony options for cohesive transitions.

Instructions

Generate a CSS gradient from a base color with automatic color stop generation.

Supports linear and radial gradients with configurable angle and number of stops. Color stops are generated using color theory for harmonious transitions.

Args:

  • base_color (string): Hex color code for the gradient base (e.g. "#6366F1")

  • type (string, optional): Gradient type — 'linear' or 'radial'. Default: 'linear'

  • angle (number, optional): Gradient angle in degrees for linear gradients (0-360). Default: 135

  • stops (number, optional): Number of color stops (2-5). Default: 3

  • direction (string, optional): Color shift direction — 'analogous' (nearby hues), 'complementary' (opposite hue), 'triadic' (spread hues). Default: 'analogous'

  • response_format (string, optional): 'markdown' or 'json'. Default: 'markdown'

Returns: CSS gradient string, color stops, and raw values.

Examples:

  • Purple linear gradient: base_color="#6366F1", angle=135

  • Blue to orange complementary gradient: base_color="#3B82F6", direction="complementary"

  • Radial triadic gradient: base_color="#10B981", type="radial", direction="triadic"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoGradient typelinear
angleNoAngle in degrees (linear only)
stopsNoNumber of color stops (2-5)
directionNoColor shift directionanalogous
base_colorYesBase hex color (e.g. '#6366F1' or '6366F1')
response_formatNoOutput formatmarkdown
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds context that color stops are generated automatically using color theory, and it describes the return values, which is useful given the lack of an output schema.

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 well-structured with clear sections for arguments, returns, and examples. It is somewhat lengthy but appropriate for the six parameters it documents, avoiding redundancy beyond the helpful examples.

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?

For a tool with six parameters and no output schema, the description covers all necessary information: parameter semantics, return value composition, and usage examples. It is sufficient for an agent to invoke the tool correctly.

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?

The input schema covers 100% of parameters, and the description enriches them with examples, default values, and explanations of direction values (analogous, complementary, triadic). This goes beyond the schema's brief 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 identifies the tool as generating CSS gradients from a base color, with specific mention of linear/radial types and automatic color stop generation. It distinguishes itself from sibling tools like ui_generate_color_palette by focusing on gradients.

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?

The description does not explicitly state when to use this tool over alternatives, but provides examples of different gradient configurations, implying its use case. No exclusions or alternative recommendations are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lnksoul1/prism-ui-design-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server