Skip to main content
Glama

match_theme_color

Read-onlyIdempotent

Match a color to a CSS theme variable, using optional usage context and a confidence threshold to identify the intended theme token.

Instructions

Find the closest matching theme variable for a given 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": {
      "color": "<color>",
      "themeCSS": "<themeCSS>"
    },
    "name": "match_theme_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYesColor to match (hex, rgb, hsl)
contextNoUsage context for better matching
themeCSSYesCSS containing theme variables
minConfidenceNoMinimum confidence threshold (0-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that — it does not say what happens when no variable meets minConfidence, whether a fallback is returned, or how confidence is scored.

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 redundancy. It is efficient, though its brevity leaves several behavioral questions unanswered rather than being optimally informative.

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 full annotations and complete schema coverage, the minimal description is workable, but there is no output schema and the description never indicates the return shape (matched variable plus confidence score, presumably). For a matching tool whose result quality depends on a threshold, that is a meaningful 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 all four parameters documented including the context enum and the minConfidence default/range, so the baseline is 3. The description contributes no additional meaning about how color formats or context affect matching.

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 gives a specific verb ('Find the closest matching') and resource ('theme variable') scoped to a given color, so the agent can tell it apart from siblings like match_theme_colors_batch or generate_theme_css. It stops short of naming an alternative explicitly, so it is not a 5.

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, no prerequisites, and no mention of the batch sibling as the alternative for multiple colors. Usage is only inferable from the phrase 'for a given color'.

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