Skip to main content
Glama

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

Names that peaked in a decade

baby_names_of_a_decade
Read-onlyIdempotent

Which names were at their most popular in a decade ("1950s names", "90s names")? Names whose share of births peaked then. 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": {
      "decade": "<decade>"
    },
    "name": "baby_names_of_a_decade"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoF or M, as recorded by SSA. Leave out for both.
limitNoHow many names, 1-200 (default 25).
decadeYesA decade from 1880 to the latest: 1950 or 1950s.
minBirthsNoOnly names with at least this many births in the decade (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the key behavioral definition — 'peaked' means share of births, not raw count — which is genuine value beyond the annotations. It says nothing about ordering, pagination, or what a result record contains.

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 substantive content is two tight, front-loaded sentences that define the tool well. The trailing 'More APIs from FitzTopPicks' line with UTM parameters is marketing noise that consumes attention without helping an agent invoke the tool. The core is efficient; the payload is diluted.

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?

For a four-parameter read-only query with full schema coverage and clear annotations, the description covers the conceptual core (what 'peaked' means). It omits anything about result shape or ordering, and there is no output schema to compensate. Adequate, but not fully self-sufficient.

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%, with each parameter (sex, limit, decade, minBirths) documented in-schema, so the baseline is 3. The description's "1950s names"/"90s names" examples loosely echo the decade format already stated in the schema ('1950 or 1950s') and add no new constraint or default information.

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 a specific verb-like concept and resource: names whose share of births peaked in a given decade, with parenthetical query examples. This is meaningfully distinct from 'top names' or 'trending names', so an agent can tell what question it answers. It does not explicitly contrast itself with the sibling baby-name tools, which keeps it short of a 5.

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?

The examples "1950s names" and "90s names" implicitly signal the intended use case of asking about a decade's signature names. However, there is no explicit statement of when to prefer this over top_baby_names, trending_baby_names, or baby_name_history, and no exclusions or prerequisites are given. Usage is inferable but not guided.

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