Skip to main content
Glama

analyze_color_likability

Read-onlyIdempotent

Checks if a color is universally disliked, such as dark yellow-green linked to biological waste, and returns a fixed alternative when needed.

Instructions

Check if a color is universally disliked (dark yellow-green associated with biological waste) and get a fixed version if needed

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>"
    },
    "name": "analyze_color_likability"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYesColor to analyze (hex, rgb, hsl, etc.)
autoFixNoAutomatically return fixed version if disliked

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, it discloses the concrete detection heuristic and that a fixed version is provided conditionally, consistent with a non-mutating operation. For this small tool that is useful context, although the replacement strategy and precise result structure remain unspecified.

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?

One front-loaded sentence conveys the test, heuristic, and optional fix without filler. The parenthetical is substantive rather than redundant.

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

Completeness4/5

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

Together with the fully described two-parameter schema and safety annotations, this is sufficient to select and invoke a simple single-color analysis. Explicit sibling-selection guidance and some result-shape or replacement-strategy detail are missing, with the former output gap more noticeable because there is no output schema.

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?

Both parameters already have full schema descriptions, including accepted color forms and autoFix's conditional behavior and default, so the baseline is 3. The description's 'if needed' reinforces conditional fixing but adds no parameter syntax, constraints, or default 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 gives a specific verb and resource—checking one color's likability—and narrows the test to dark yellow-green associated with biological waste, while also mentioning an optional corrected color. It does not explicitly distinguish this single-color check from sibling analysis, adjustment, or batch-fixing tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The wording supplies a clear use case: screen a color for this particular disliked appearance and obtain a replacement when necessary. It gives no explicit when-not guidance or routing to sibling tools for broader color analysis, general adjustment, or multiple colors.

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