Skip to main content
Glama

analyze_skin_tone

Analyzes skin, eye, lip, eyebrow, and hair colors from a selfie for cosmetic color reading only; not medical or identity assessment.

Instructions

Read skin, eye, lip, eyebrow and hair colours from a selfie (YouCam AI Facial Color Tones Analyzer). Costs 20 units on success. Cosmetic colour reading only, not a medical or identity assessment.

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": "analyze_skin_tone"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
face_angle_strictnessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description's 'Costs 20 units on success' is real added information the agent can't get elsewhere — it tells the caller the operation is metered and only charged on success. It stops short of explaining latency, failure modes, or the async task_ref behaviour beyond what the schema states.

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?

Three short sentences: what it reads, what it costs, what it is not. The scope and cost are front-loaded and no sentence is filler.

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 three-parameter analysis tool with no output schema, the description covers purpose, cost and scope well. The remaining gap is that it says nothing about the shape of the returned colour data or the polling path when wait_seconds is exceeded, which matters for a tool that can return a task_ref.

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 coverage is 67%: person_image and wait_seconds are well documented inline, but face_angle_strictness has no description in the schema and the tool description does nothing to explain its five enum levels or default behaviour. With the schema carrying most of the load, this lands at the baseline rather than above it.

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?

The description names a specific verb and resource set: 'Read skin, eye, lip, eyebrow and hair colours from a selfie.' It also names the underlying analyzer and adds a scope boundary ('cosmetic colour reading only'), which makes it unambiguous against siblings like try_hair_color or try_on_clothes that also take a person image.

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?

There is a genuine when-not-to-use statement ('not a medical or identity assessment') and a cost signal, but no explicit guidance on when to pick this over the sibling try_* tools or what preconditions apply to the selfie. Usage is implied rather than spelled out.

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