Nameidea

Get a recorded surname

get_surname_record

Read-onlyIdempotent

Look up a stable surname ID returned by search_surnames, with Census rank, count, source and actual collection pages. not_found applies only to this 3,000-record subset.

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": {
      "id": "<id>"
    },
    "name": "get_surname_record"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Stable surname ID, for example smith. Case-insensitive.

Output Schema

Name	Required	Description	Default
`record`	Yes
`source`	Yes
`status`	Yes
`warnings`	Yes
`dataVersion`	Yes
`datasetCounts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the scoping of failure (not_found is confined to a 3,000-record subset) and the data provenance of the ID. No auth or rate-limit detail, so not a 5.

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

Conciseness4/5

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

Two compact sentences with the core purpose front-loaded and the failure-scope caveat trailing. The embedded list of returned fields (Census rank, count, source, collection pages) mildly duplicates the output schema rather than earning its place, which keeps it from a 5.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile; the description correctly fills in provenance and failure semantics instead of repeating them. Remaining gaps (e.g., why the subset is limited to 3,000 records) are minor for a single-parameter read 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 coverage is 100% and the single 'id' parameter is already documented with format, pattern, and case-insensitivity in the schema. The description only reaffirms that the ID is stable and originates from search_surnames, which is marginal added meaning. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (look up) and resource (stable surname ID), and explicitly ties provenance to the sibling tool search_surnames, so an agent can separate this detail-lookup from the search tool. It also names the payload it returns (Census rank, count, source, collection pages), making the tool's role unambiguous.

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 phrase 'returned by search_surnames' makes the workflow explicit: call search first, then use this tool with the resulting ID. The caveat that not_found applies only to the 3,000-record subset gives further usage context. It stops short of an explicit when-not statement, so 4 rather than 5.

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

All Nameidea tools Inspect

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

Need Help?