Skip to main content
Glama

Face measurement statistics

get_reference_statistics
Read-only

Returns percentiles (p10, p25, median, p75, p90, min, max) and the unit of facial measurements from 102 adult faces (49 women, 53 men) of the Face Research Lab London Set, measured with a 478-point MediaPipe landmarker, plus citation and license. Use this when you need a number (e.g. median fWHR or pupillary distance by sex); use classify_face_shape to label one face's shape, get_face_type for what a type means, and get_methodology for how a measure is computed. Aggregates only; one research set photographed in one city, so these describe these faces, not a population. Read-only; unknown measure or group values are rejected with a validation error.

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

Input Schema

NameRequiredDescriptionDefault
groupNoWhich faces: all (all faces), female (women only) or male (men only). Omit to get all three groups side by side.
measureNoOne measure: composite (score, points 0-100), symmetry (percent), golden (golden ratio fit, percent), fwhr (facial width-to-height ratio), midface (midface ratio), pd (pupillary distance, mm), tilt (canthal tilt, degrees). Omit to get all seven.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / group / description
      Previous value: -"all, female or male. Omit for all three."New value: +"Which faces: all (all faces), female (women only) or male (men only). Omit to get all three groups side by side."
    • changedInput schema / properties / measure / description
      Previous value: -"One measure. Omit for all."New value: +"One measure: composite (score, points 0-100), symmetry (percent), golden (golden ratio fit, percent), fwhr (facial width-to-height ratio), midface (midface ratio), pd (pupillary distance, mm), tilt (canthal tilt, degrees). Omit to get all seven."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), yet the description adds substantial context beyond them: the result is aggregates only, drawn from one research set photographed in one city so it does not describe a population, and unknown measure/group values are rejected with a validation error. The generalizability caveat and error behavior are exactly the kind of disclosure structured fields cannot carry.

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?

Front-loaded with the return payload, then usage routing, then caveats — a logical progression with no filler sentences. It is on the long side, with a dense parenthetical provenance clause in sentence one, but each clause carries information an agent would otherwise have to guess.

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 compensates by enumerating the returned statistics, the unit, and the bundled citation/license. It also covers the two-parameter optional-input behavior implicitly ('omit to get all') and the validation failure mode, leaving no material gap for a zero-required-parameter read-only query tool.

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 100% and both parameters are enums fully documented in the schema, so the schema already does the heavy lifting. The description only adds incidental framing ('median fWHR or pupillary distance by sex') that hints at the group dimension without adding format or default details beyond the schema — the baseline 3 applies.

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+resource and enumerates exactly what comes back (percentiles p10–p90, min/max, unit, citation, license). It also pins down the data provenance (102 faces, 49 women/53 men, Face Research Lab London Set, 478-point MediaPipe landmarker), which distinguishes it unambiguously from sibling tools like classify_face_shape and get_face_type.

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 gives an explicit when-to-use trigger ('when you need a number, e.g. median fWHR or pupillary distance by sex') and then routes three named alternatives — classify_face_shape for labeling a single face, get_face_type for interpreting a label, get_methodology for computation details — each with its own selecting condition.

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.