Skip to main content
Glama

Methodology, thresholds and validity

get_methodology
Read-only

Returns how the numbers are made, as one object: the landmark model (478-point MediaPipe) and engine version, every classification threshold (face shape, eye, lip, nose, pupillary distance), how the 1-10 score is built, its validity against 2,513 human raters on the same faces (Spearman correlations with 95% intervals; the score did not predict them) and notes, optionally with the dated change history. Use this to explain or check how a number, threshold or score is computed, or whether the score means anything; use get_reference_statistics for the measured values themselves, get_face_type for one type's rule, and get_citation for how to credit the data. Read-only; the response is large.

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_methodology"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_changelogNotrue to also return the dated method change history (changelog entries). Default false: methodology only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include_changelog / description
      Previous value: -"Also return the dated change history."New value: +"true to also return the dated method change history (changelog entries). Default false: methodology only."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), but the description adds a material operational warning that the response is large, which affects how an agent should call it. It also discloses a substantive content fact up front — that the score did not predict human ratings — which shapes how the returned validity data should be interpreted. Minor gap: it doesn't quantify how large the response is or whether the changelog materially inflates it.

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?

Purpose is front-loaded, then the content inventory, then the routing sentence — a sensible order with no filler sentences. It is dense, however: one very long sentence carries a heavy parenthetical, and the "Read-only" clause duplicates the annotation.

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?

There is no output schema, so the description must describe the return value itself, and it does so in detail — model identity, thresholds, score construction, correlations with confidence intervals, notes, and optional changelog. For a zero-required-parameter read tool, an agent has everything needed to call it and interpret the result.

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 the single parameter already carries a description stating the true/default-false behavior. The description's "optionally with the dated change history" restates that rather than adding syntax or format insight. Baseline 3 is appropriate when the schema does the work.

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?

Specific verb+resource ("Returns how the numbers are made") followed by an enumeration of exactly what the object contains: landmark model and engine version, every classification threshold, the 1-10 score construction, validity against 2,513 raters, and notes. An agent can tell this apart from get_reference_statistics, get_face_type, and get_citation 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 Guidelines5/5

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

Explicit when-to-use ("explain or check how a number, threshold or score is computed, or whether the score means anything") and explicit routing to three named alternatives with the condition that selects each. Nothing about sibling selection is left to inference.

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.