Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

A baby name's popularity since 1880

baby_name_history
Read-onlyIdempotent

How popular has a first name been in the US? Yearly counts and ranks of babies given the name since 1880 (US Social Security data), its peak year and best rank. Use for "how popular was Olivia in 1990" or "when did Jayden peak". More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "name": "<name>"
    },
    "name": "baby_name_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast year of the series (default: the latest year).
sexNoF or M, as recorded by SSA. Leave out for both.
fromNoFirst year of the series (default 1880).
nameYesA first name as SSA spells it: 2-15 letters A-Z, any case ("olivia" works). Spaces, hyphens and apostrophes are dropped like SSA drops them ("Mary-Kate" → "Marykate"). Accents are read as plain letters ("Sofía" finds "Sofia").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description usefully adds data provenance (US Social Security data, series starting 1880) and hints at return contents (peak year, best rank). It says nothing about edge cases such as names with no SSA record or out-of-range years, which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded and dense with useful routing information. The trailing 'More APIs from FitzTopPicks' sentence with a UTM-tagged URL is promotional filler that does not help an agent select or invoke the tool, costing it a point.

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

Completeness4/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 does the right thing by sketching the returned values (yearly counts and ranks, peak year, best rank). Combined with a fully documented four-parameter schema and complete annotations, an agent has enough to call it correctly; only edge-case behavior and result size/shape are left 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 100% and the schema documents every parameter in detail, including the name normalization rules and the 1880 floor on 'from'. The description only restates the 1880 start year and adds no syntax or semantics beyond the schema, so the baseline of 3 applies.

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 opens with a specific question it answers ('How popular has a first name been in the US?') and names the concrete resource: yearly counts and ranks since 1880 plus peak year and best rank. It is clearly about one name's time series, which separates it in spirit from siblings like top_baby_names or compare_baby_names, but it never names or contrasts an actual sibling.

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

Usage Guidelines4/5

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

It gives an explicit 'Use for' clause with two concrete example queries ('how popular was Olivia in 1990', 'when did Jayden peak') that map well onto the tool's capability. There are no when-not conditions or named alternatives, so routing relies on the agent inferring from its sibling list.

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