Skip to main content
Glama

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

Babies listed per year

baby_name_totals
Read-onlyIdempotent

How many babies and distinct names the US Social Security lists record per year and sex, nationally or by state (the base for per-million shares). 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": "baby_name_totals"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast year (default: the latest).
sexNoF or M, as recorded by SSA. Leave out for both.
fromNoFirst year (default: the first year of that data).
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

B3.2/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 useful scope context (national vs. state aggregation, SSA as the source, role as a denominator), but says nothing about aggregation shape, defaults applied, or result size for wide year ranges.

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 sentence is front-loaded and reasonably tight. The trailing 'More APIs from FitzTopPicks' link with UTM parameters is pure promotion, contributes nothing to tool selection, and dilutes an otherwise compact definition.

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?

All four parameters are optional and fully documented in the schema, and there is no output schema, so the description does need to convey the return shape. It does so acceptably by stating that it reports counts of babies and distinct names per year and sex, nationally or by state; only the exact response fields and ordering are 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 coverage is 100%, so the schema already documents 'from', 'to', 'sex' and 'state' including defaults and the enum. The description reinforces the axes ('per year and sex, nationally or by state') but adds no syntax or edge-case meaning beyond that, which is the baseline case for full schema coverage.

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 the resource precisely: counts of babies and distinct names from the US SSA, sliced by year and sex, nationally or by state. That is specific enough to distinguish it from name-lookup siblings like baby_name_history or top_baby_names, though it does not explicitly contrast with baby_name_by_state, which overlaps on the state dimension.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or exclusion. The parenthetical '(the base for per-million shares)' hints at a normalization use case, but the agent is left to infer whether this or baby_name_by_state / baby_name_history is the right call for a given question.

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