Skip to main content
Glama

Classify a face shape from four measurements

classify_face_shape
Read-only

Runs the same seven-rule face shape classifier as thefaceanalysis.com/face-shape-detector on four distances and returns the shape (oval, round, square, heart, oblong, diamond or triangle), the rule that matched, the four ratios it used, and links to the methodology and detector. Rules are checked in a fixed order (oblong, triangle, round, square, heart, diamond) and oval is the fallback when none match; only ratios matter, so any consistent unit works. Use this when you already have the four distances; it does not look at photos: to measure a photo, use the widget (get_embed_snippet) or the site, and use get_face_type for what a shape means. Borderline faces can flip between two shapes; no accuracy figure is claimed because the reference set has no labelled face types. Read-only; zero, negative or missing values are rejected with a validation error.

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": {
      "face_length": "<face_length>",
      "cheekbone_width": "<cheekbone_width>",
      "forehead_width": "<forehead_width>",
      "jaw_width": "<jaw_width>"
    },
    "name": "classify_face_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
jaw_widthYesJaw width, measured across the jaw. Positive number, same unit.
face_lengthYesFace length: top of the forehead surface (hairline side) to the bottom of the chin. Positive number, same unit as the other three (pixels, mm, cm or landmark units).
forehead_widthYesForehead width, measured across the temples. Positive number, same unit.
cheekbone_widthYesFace width at the widest point across the cheekbones. Positive number, same unit; every ratio is taken against this or the jaw.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / cheekbone_width / description
      Previous value: -"Widest point across the cheekbones"New value: +"Face width at the widest point across the cheekbones. Positive number, same unit; every ratio is taken against this or the jaw."
    • changedInput schema / properties / face_length / description
      Previous value: -"Top of the forehead surface to the bottom of the chin"New value: +"Face length: top of the forehead surface (hairline side) to the bottom of the chin. Positive number, same unit as the other three (pixels, mm, cm or landmark units)."
    • changedInput schema / properties / forehead_width / description
      Previous value: -"Width across the temples"New value: +"Forehead width, measured across the temples. Positive number, same unit."
    • changedInput schema / properties / jaw_width / description
      Previous value: -"Width across the jaw"New value: +"Jaw width, measured across the jaw. Positive number, same unit."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the fixed rule order, oval as fallback, that ratios alone matter, that borderline faces can flip, that no accuracy figure is claimed, and that zero/negative/missing values are rejected with a validation error — context the annotations cannot convey.

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?

It is one dense paragraph, but it is front-loaded with purpose and output shape before the caveats, and each clause carries information; a few ideas (rule order, borderline flips, validation) are packed tightly enough to slow reading.

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?

With no output schema, the description fully specifies the return payload (shape, matched rule, four ratios, methodology/detector links) and covers failure modes and interpretation limits, so an agent has everything needed to call and use the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter is already documented, so baseline would be 3; the description adds a genuinely useful semantic point that only ratios matter, hence any consistent unit works, and that every ratio is normalized against cheekbone or jaw.

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 opens with a specific verb and resource ('Runs the same seven-rule face shape classifier ... on four distances') and enumerates the outputs (shape, matched rule, four ratios, links), making it immediately distinguishable from siblings like get_face_type and list_face_types.

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

Usage Guidelines5/5

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

It says explicitly when to use it ('when you already have the four distances'), states what it does not do ('does not look at photos'), and routes the agent to alternatives: get_embed_snippet or the site for measuring a photo, get_face_type for interpreting a shape.

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.