Skip to main content
Glama

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

Similar baby names

similar_baby_names
Read-onlyIdempotent

Spelling variants of a first name (Kaitlyn, Katelyn, Caitlin...) and names whose popularity rose and fell the same way. Use for "names like Emma" suggestions. 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": "similar_baby_names"
  }
}

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").
limitNoNames per list, 1-50 (default 10).

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 cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds meaningful context the annotations cannot: it defines the two similarity signals (spelling distance and co-trending popularity), which prevents the agent from assuming semantic/origin/cultural similarity.

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 two substantive sentences are front-loaded and efficient. The third sentence is pure promotional copy for other APIs (a UTM-tagged URL) that does not help an agent select or invoke this tool, so a third of the description does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple 3-parameter read tool with full schema coverage, complete annotations, and no output schema, so the description need not explain return values. The one real gap is whether the two similarity modes return separate lists (the limit description says 'names per list'), but that ambiguity is minor for a tool of this complexity.

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 (hyphens dropped, accents folded) and the sex/limit defaults, so the schema carries parameter meaning. The description only illustrates the name parameter via the Emma example and adds nothing about sex or limit, so 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 the resource (first-name variants) and defines similarity concretely: 'Spelling variants ... and names whose popularity rose and fell the same way', with examples (Kaitlyn, Katelyn, Caitlin). This distinguishes it from trend/history siblings by telling the agent roughly what 'similar' means, though it never states the action verb ('find/list returns similar names') 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?

'Use for "names like Emma" suggestions' gives one positive use case, which is real guidance. There is no when-not guidance and no named alternative (e.g. baby_name_history or trending_baby_names) for an agent that actually wants trend data rather than name suggestions, so the agent must infer boundaries.

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