Skip to main content
Glama

generate_material_theme

Read-onlyIdempotent

Creates a complete Material Design 3 color theme from a source color, with optional custom palettes for consistent UI styling.

Instructions

Generate a complete Material Design 3 color 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_material_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceColorYesSource color for theme generation
includeCustomColorsNoInclude custom color palettes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/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 fully covered. The description adds nothing beyond that - it doesn't say what 'complete' produces (which roles or tokens), whether the result is deterministic, or anything about output shape, which matters given there is no 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the artifact being produced is stated first and the input second. Nothing is wasted or padded.

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?

For a two-parameter, annotated, read-only tool this is minimally sufficient, but with no output schema the description should indicate what a 'complete' theme contains so the agent knows what it will receive. Core invocation information is present; result expectations are not.

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 are already documented, and the description only restates that generation comes from a source color. It adds no meaning about accepted color formats or what includeCustomColors actually adds to the theme.

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 uses a specific verb (Generate), names a concrete artifact (a complete Material Design 3 color theme), and states its input (a source color). That distinguishes it reasonably well from siblings like generate_theme_css or generate_tonal_palette, though it never explicitly contrasts itself with them.

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?

Usage is only implied: an agent can infer 'use this when you need a full MD3 theme from one color.' There is no explicit when-to-use, when-not-to-use, or pointer to related tools such as generate_theme_css for output formatting or generate_tonal_palette for single ramps.

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