Skip to main content
Glama
Sign In

NobodyNamed

by io.github.michaelcolenso
OverviewDiscussionsAdmin

get_name_data

Returns full yearly birth count timeseries (1880–2025) for a given name for both sexes, including trend classification (rising/stable/declining/endangered/extinct), peak year, and peak count.

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": "get_name_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe baby name to look up (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does provide useful detail about the response contents (timeseries, trend categories, peak stats), but it does not disclose behavior for unknown names, whether the timeseries is separated by sex, or any potential limitations or errors. This is acceptable for a read-only lookup but not rich.

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

Conciseness5/5

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

The description is a single sentence that efficiently front-loads the main action and resource, then lists specific output attributes. There is no filler or redundancy, making it highly concise and well-structured.

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?

Given the absence of an output schema, the description does a solid job of enumerating return contents: yearly timeseries, trend classification, peak year, and peak count. It lacks edge-case details (e.g., name not found) and does not clarify whether the series is split by sex, but these are minor for a simple one-parameter 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?

The schema has one parameter with 100% coverage, including case-insensitivity. The tool description adds no additional parameter semantics beyond what the schema already states, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a full yearly birth count timeseries (1880–2025) for a specified name, including trend classification, peak year, and peak count. This specific verb+resource combination distinguishes it from sibling tools like get_name_debuts or get_names_by_status.

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

Usage Guidelines4/5

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

The description implies the tool is for retrieving comprehensive historical data for a single name, providing clear context for when to use it. However, it does not explicitly mention alternative tools or conditions when this tool should not be used, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NobodyNamed toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources