Skip to main content
Glama

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

Rising and falling baby names

trending_baby_names
Read-onlyIdempotent

Which baby names rose or fell the most between two years, nationally or in a state? Biggest risers and fallers by share, rank or percent change. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault
byNoSort order for risers and fallers.
toNoLater year (default: the latest).
sexNoF or M, as recorded by SSA. Leave out for both.
fromNoEarlier year (default: one year before "to").
limitNoNames per list, 1-100 (default 10).
stateNoTwo-letter state or territory code; leave out for the US.
minCountNoMinimum count in a year for a name to qualify, 5-100000 (default 100 nationally, 20 for a state).

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 by structured data. The description adds little beyond that: it restates the sort modes already enumerated in the schema and discloses nothing about default year selection, ranking direction, response shape, or what happens with sparse data. With annotations carrying the behavioral load, a 3 is fair.

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 core content is two tight sentences that front-load the question the tool answers. However, the trailing 'More APIs from FitzTopPicks' link with UTM parameters is promotional noise that consumes roughly a third of the text and provides no decision value to an agent.

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?

Seven optional parameters with two enums and no output schema make this a moderately complex tool, and the description does not describe the returned lists (fields, ordering direction, ties, empty results). Full schema coverage and complete annotations mitigate this, but for a tool whose whole output is a ranked risers/fallers list, some note on the response would materially help.

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%, so every one of the seven parameters (by, from, to, sex, state, limit, minCount) is already documented with types, defaults and ranges. The description only echoes 'between two years', 'nationally or in a state' and the three sort modes, adding no syntax or interpretation beyond the schema. Baseline 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 names a specific analytical operation (which names rose or fell the most between two years) plus its two scoping axes (national vs. state). That is enough to separate it from siblings like top_baby_names or compare_baby_names, though it never names those alternatives explicitly.

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?

Usage is implied only through the opening question 'Which baby names rose or fell the most between two years' — the agent can infer the intended question this tool answers. There is no explicit when-to-use, when-not-to-use, or pointer to a competing sibling, so guidance stays at the implied level.

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