Skip to main content
Glama

generate_theme_css

Read-onlyIdempotent

Generate CSS custom properties for a complete color theme from a single source color, with configurable prefixes and tone values for consistent design tokens.

Instructions

Generate CSS custom properties for a complete theme from a source color

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sourceColor": "<sourceColor>"
    },
    "name": "generate_theme_css"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixNoPrefix for CSS variables (e.g., 'color' → --color-primary-50)color
sourceColorYesSource color for theme generation
includeTonesNoTone values to include (default: 0,10,20,30,40,50,60,70,80,90,95,99,100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description adds only the notion of a full theme being emitted as CSS custom properties, and says nothing about the shape of the returned CSS or how tone ranges affect output volume.

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?

A single front-loaded sentence with no filler or repetition. It is perhaps too lean given the sibling ambiguity, but nothing in it is wasted.

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

Completeness3/5

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

With no output schema, the description should say what comes back — a CSS string, an object of variables, a full stylesheet — and it does not. For a three-parameter, read-only generator this is a noticeable but not fatal gap.

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 prefix and includeTones documented in the schema itself, so the baseline is 3. The description reinforces that sourceColor drives generation but adds no format or syntax detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and artifact ('Generate CSS custom properties for a complete theme') plus the input ('from a source color'), so an agent knows it produces CSS variables, not a palette object. It does not explicitly distinguish itself from close siblings such as generate_material_theme or refactor_css_with_theme.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite a crowded sibling set of theme/palette generators. The agent must infer from the phrase 'complete theme' that this is the CSS-emitting option rather than a raw palette tool.

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