Skip to main content
Glama

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

Top baby names of a year

top_baby_names
Read-onlyIdempotent

What were the most popular baby names in a year, nationally or in one US state? Ranked lists for girls and boys (US Social Security data). 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": "top_baby_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoF or M, as recorded by SSA. Leave out for both.
yearNoYear (default: the latest).
limitNoHow many names per sex, 1-1000 (default 10).
stateNoTwo-letter code: AK, AL, AR, AZ, CA, CO, CT, DC, DE, FL, GA, HI, IA, ID, IL, IN, KS, KY, LA, MA, MD, ME, MI, MN, MO, MS, MT, NC, ND, NE, NH, NJ, NM, NV, NY, OH, OK, OR, PA, RI, SC, SD, TN, TX, UT, VA, VT, WA, WI, WV, WY;

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description only needs added context. It adds the SSA data source and the ranked boys/girls output shape; it does not discuss rate limits or authentication, but those are not suggested by this simple public-data lookup.

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?

The core use case is front-loaded in one question, followed by a compact data-source and return-shape sentence. The promotional “More APIs” sentence is extraneous and keeps it from being maximally tight.

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?

For a simple four-parameter lookup with no output schema and full schema descriptions, the definition gives enough scope, source, and output shape to call it correctly. It could be more complete with explicit alternative routing, but the schema and “ranked lists” cover the essentials.

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%, so the schema already documents sex, year, limit, and state. The description adds useful scope clarification that omitting state means national results and that girls/boys lists are returned, but it says nothing about limit and adds no syntax beyond the schema.

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 question form names the resource (popular baby names), the time scope (a year), and the geography (national or one US state), so the agent can tell what it returns. It does not explicitly distinguish itself from siblings such as baby_names_of_a_decade or trending_baby_names, which keeps it below 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 opening question supplies a clear use case, but there is no explicit when-not guidance and no named alternative such as trending_baby_names or baby_names_of_a_decade. Usage is implied rather than routed.

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