Skip to main content
Glama

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

A baby name in every US state

baby_name_by_state
Read-onlyIdempotent

Where in the US is a first name most popular? The name's count and rank in every state and territory for one year, and the state where its share is highest. 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_by_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexNoF or M, as recorded by SSA. Leave out for both.
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").
yearNoYear, 1910 or later (territories from 1998). Default: the latest year with state data for this name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description still adds real value beyond them: the scope is one year, output covers every state and territory, and the default year is the latest with data for that name (only implied by the schema).

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

Conciseness2/5

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

The first sentence is a well-placed, front-loaded framing of the question. However, the promotional 'More APIs from FitzTopPicks' URL with UTM parameters consumes roughly half the text and contributes nothing to tool selection or invocation.

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 three simple parameters, full schema coverage, and no output schema, the description covers the main risk (which year is used by default) and the shape of the result. It does not address ordering, pagination, or how the highest-share state is chosen, which leaves minor gaps for a data-returning tool.

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%, including normalization rules for name and the sex enum, so the schema carries the parameter semantics. The description only adds the implicit 'one year' framing for the year parameter and adds no new syntax or edge-case detail. 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?

Names a specific resource and output shape: count and rank of a first name in every state and territory for one year, plus the state with the highest share. It is clear enough to separate from timeline-style siblings such as baby_name_history, but it never explicitly names an alternative or states how it differs.

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 ('Where in the US is a first name most popular?') implies the use case, so guidance is present but indirect. There is no explicit when-to-use/when-not, and no mention of alternatives among the many sibling baby-name tools.

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