Skip to main content
Glama

try_hair_color

Recolour a person's hair using a preset shade or custom hex color; provide a JPEG or PNG image under 1920 px on the long side.

Instructions

Recolour a person's hair (YouCam AI Hair Color). Costs 1 unit on success. Give exactly one of preset or color (#RRGGBB). Image long side must be under 1920 px.

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": {
      "person_image": "<person_image>"
    },
    "name": "try_hair_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNo
presetNo
person_imageYesAn https:// image URL on this server's allowlist, or an image_ref (img_...) returned by an earlier call in this session. JPEG or PNG.
wait_secondsNoSeconds to wait for the result before returning a task_ref to poll. Default 60.
color_intensityNo
shine_intensityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, open-world operation; the description adds real value on top by disclosing a 1-unit charge on success and an input resolution ceiling of 1920 px on the long side. The async nature (a task_ref comes back for polling) is only surfaced indirectly through the wait_seconds parameter description, so it is not fully spelled out here.

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?

Four short sentences, each carrying distinct information — action, cost, argument exclusivity, input constraint — with the core action front-loaded. No filler or redundancy.

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?

For a six-parameter mutation tool with no output schema, the description covers the essentials an agent needs before calling: what it does, what it costs, and how to combine the mutually exclusive style arguments. The unexplained intensity knobs and the polling path via get_task_status are the remaining gaps.

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 33%, and the description compensates for the most important gaps: the mutual exclusivity of preset and color and the #RRGGBB format. It says nothing about color_intensity or shine_intensity, both of which are bare 0-100 integers in the schema with no explanation anywhere.

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

Purpose5/5

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

States a specific verb and resource — 'Recolour a person's hair' — and names the underlying capability (YouCam AI Hair Color), which cleanly separates it from try_hairstyle and try_on_clothes. An agent can pick this tool without opening any schema.

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?

Gives a hard selection rule: 'Give exactly one of preset or color (#RRGGBB)', which is the main way to misuse this tool. It does not, however, say when to prefer a preset over a free-form hex, or when a sibling like try_hairstyle would be the better call.

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