Skip to main content
Glama

Calculate a sourced height percentile

height_percentile
Read-onlyIdempotent

Use WHO 2007 ages 61–228 months or CDC/NHANES US adult 2021–2023 measured height quantiles. Returns source, population, interpolation method and tail bounds.

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": {
      "height": "<height>",
      "population": "<population>",
      "reference_sex": "<reference_sex>"
    },
    "name": "height_percentile"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNometric
heightYesA height such as 170 cm, 1.85 m or 5 ft 11 in. Bare numbers follow the selected input units.
age_monthsNoWHO 2007 only. Ages 61–228 months, including fractional months.
populationYes
reference_sexYes
adult_age_groupNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / age_months / description
      Added value: +"WHO 2007 only. Ages 61–228 months, including fractional months."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile -- read-only, idempotent, non-destructive, closed-world -- so the description's marginal value is the return-content disclosure. That disclosure is genuinely useful. It names the four result fields (source, population, interpolation method, tail bounds), so an agent knows the percentile arrives with provenance and extrapolation caveats. However, it says nothing about the percentile scale or units, how tail bounds are applied, or how the accuracy degrades at the extremes.

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?

Two sentences, both front-loaded with the reference constraints first and the return contract second. It is dense and telegraphic but there is essentially no filler.

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

Completeness3/5

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

With six parameters, three of them required, and no output schema, the description does only partial work. It covers population choice and the age window lightly and lists the returned fields. It omits the interaction rules between population, age_months and adult_age_group, and leaves the percentile output format unstated.

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 only 33%: height and age_months are documented in the schema, while population, reference_sex, adult_age_group and units have no per-parameter description. The text partially compensates by naming the two population values and restating the 61–228-month constraint. It does not explain the month-to-year semantics of adult_age_group, the meaning of reference_sex, or that adult_age_group is irrelevant for who2007.

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?

The description names the specific reference datasets (WHO 2007 for ages 61–228 months, CDC/NHANES US adult 2021–2023 measured quantiles), which makes the resource and its scope concrete and separates it from convert_height and compare_heights. The actual verb is left implicit -- the word 'percentile' only appears in the name and title, not in the sentence itself.

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?

Routing guidance is implied by the reference data constraints: WHO 2007 covers ages 61–228 months and CDC/NHANES covers US adults, so an agent can infer which population fits which subject. There is no explicit statement of when to prefer it over a sibling tool, no note that both populations cannot apply at once, and no guidance on what to do outside the age range.

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