Skip to main content
Glama

Personal Colour Analysis: Find Your Colours

image_personal
Read-only

Upload a portrait photo and receive a full personal colour analysis. Determines your seasonal type (Spring, Summer, Autumn, or Winter), colour depth (light, medium, or deep), and undertone (warm, cool, or neutral). Returns a curated palette of archive colours that genuinely suit the subject, each with full historical provenance and cultural context, plus colours to avoid. Uses Claude Vision for skin, hair, and eye analysis, then matches to the archive by CIEDE2000 perceptual distance. The photo is never stored. Example: a Deep Winter might wear Ottoman Carbon Ink while a True Spring suits Kogi Mango.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "image_personal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional: person's name for the report e.g. 'Sarah'
image_urlNoURL of a portrait photo hosted online. Easier than base64 for MCP use. Either image_url or image_base64 required.
media_typeNoImage MIME type e.g. 'image/jpeg'image/jpeg
image_base64NoBase64 encoded portrait photo (JPEG or PNG). Face should be clearly visible in natural light. Either image_base64 or image_url required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Structured JSON response. Shape varies by tool; most return an 'ok' boolean plus a 'result' or 'results' field with the tool's data payload.",
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "error": {
      -      "type": "string"
      -    },
      -    "ok": {
      -      "type": "boolean"
      -    },
      -    "result": {
      -      "type": [
      -        "object",
      -        "array",
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description is consistent with that while adding real context: it discloses the analysis pipeline (Claude Vision for skin/hair/eye, CIEDE2000 matching to the archive) and, importantly, the data-handling guarantee that 'the photo is never stored'. It does not mention latency, rate limits, or failure modes for unusable photos, keeping it short of a 5.

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?

The core capability, output contents, method, and privacy note are front-loaded in three tight sentences. The closing example ('a Deep Winter might wear Ottoman Carbon Ink while a True Spring suits Kogi Mango') is illustrative rather than essential, but it usefully conveys the flavour of results without bloat.

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

Completeness5/5

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

For a single-photo analysis tool with a full output schema, the description covers what it does, what it returns, how it computes it, and what happens to the uploaded data. Nothing an agent needs in order to decide to call it is missing.

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%, so all four parameters (name, image_url, media_type, image_base64) are already documented, including the either/or requirement. The description adds no parameter-level detail beyond that baseline, which is acceptable but not value-adding.

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?

Opens with a concrete verb+resource pair ('Upload a portrait photo and receive a full personal colour analysis') and enumerates the specific outputs: seasonal type, colour depth, undertone, matching palette, and colours to avoid. That scope is clearly distinct from generic palette-extraction siblings such as extract_image_colours or image_palette, though no sibling is named to make the distinction explicit.

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?

Usage is implied by the portrait-photo framing and the input requirements ('Face should be clearly visible in natural light'), so an agent can infer this is the tool for analysing a person rather than an arbitrary image. However, there is no explicit when-to-use/when-not guidance and no named alternative for non-portrait colour extraction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources