Skip to main content
Glama

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

Compare baby names over time

compare_baby_names
Read-onlyIdempotent

How do up to 5 first names compare in popularity over the years? Yearly series side by side. 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": {
      "names": "<names>"
    },
    "name": "compare_baby_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast year (default: the latest).
sexNoF or M, as recorded by SSA. Leave out for both.
fromNoFirst year (default 1880).
namesYesUp to 5 names separated by commas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 fully covered. The description adds that results are yearly series presented side by side, which is useful output-shape context, but says nothing about data source, pagination, or whether values are counts or ranks.

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 operational content is two short, front-loaded sentences with no bloat, but the definition is then padded with a promotional URL for 'more APIs' that offers the calling agent no value and dilutes the signal.

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 read-only query tool with full schema coverage, full annotations, and no output schema, the description is adequate: it conveys the multi-name, year-series comparison shape. It still leaves return-value semantics (counts vs. ranks, series ordering) unstated, which matters given there is no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the defaults (from=1880, to=latest), the F/M enum, and the comma-separated name list are already fully documented. Param count is 4, so the description adds little new meaning beyond reiterating that at most 5 names are accepted; the schema does the heavy lifting.

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 and resource ('compare' + 'first names ... in popularity over the years') and states the scope limit of up to 5 names, which separates it from single-name tools like baby_name_history. It stops short of explicitly naming a sibling, so it is clear but not fully differentiated.

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 framing question implies the use case (comparing a small set of names over a multi-year range) but gives no explicit when-to-use or when-not-to-use guidance, and no alternatives are named despite several nearby baby-name siblings.

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