Skip to main content
Glama

harmonize_colors

Read-onlyIdempotent

Adjust a set of colors so they work better together using Material Design algorithms, with configurable strength and method.

Instructions

Harmonize colors to work better together using Material Design algorithms

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": {
      "colors": "<colors>"
    },
    "name": "harmonize_colors"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorsYesArray of colors to harmonize
factorNoHarmonization strength (0-1)
methodNoHarmonization methodharmonize

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that, the description adds only the vague phrase "using Material Design algorithms" — it does not say whether input colors are returned in the same order/count, how the three methods differ in effect, or what the result looks like.

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 compact sentence with no filler and the core action front-loaded. It is efficient, though its brevity comes at the cost of useful detail rather than from tight editing of rich content.

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

Completeness2/5

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

Three parameters, one enum, and no output schema — the description should at least say what is returned. Instead it leaves the return value, ordering behavior, and method semantics undocumented, which is thin for a transformation tool operating on 2-10 colors.

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%: colors, factor (0-1 strength), and the method enum are all documented in the schema. The description adds nothing about them, so the baseline of 3 applies; it offers no interpretation of how factor or method change the outcome.

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

Purpose3/5

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

"Harmonize colors ... using Material Design algorithms" names a verb and resource, but it largely restates the tool name; "work better together" is vague about what the output actually is (adjusted copies of the same colors, a reordered palette, new colors?). It gives no hint of how it differs from siblings such as generate_palette or match_theme_color.

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 guidance at all: no mention of when harmonization is preferable to palette generation, theme matching, or contrast fixing, and no prerequisites or exclusions. The agent must infer the use case entirely from the name.

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