Skip to main content
Glama

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

A place's names in other languages

place_names
Read-onlyIdempotent

What is a place called in other languages, and what were its historic names? Every name GeoNames lists for a place, region or country, by language. 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": {
      "geonameId": "<geonameId>"
    },
    "name": "place_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOnly these languages, comma-separated (default all 16).
historicNoInclude historic names (default true).
geonameIdYesA GeoNames ID of a place (geonameId in every result), a region or a country.
colloquialNoInclude colloquial names such as "Big Apple" (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare this as a safe, read-only, idempotent, non-destructive, non-open-world lookup. The description adds that all names are returned by language and that historic names are included, but it does not discuss response format, pagination, or error behavior.

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 purpose is stated early and compactly, but the promotional sentence about other APIs adds noise that does not help an agent select or invoke the tool. The rhetorical opening is acceptable but less efficient than a direct statement.

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?

For a simple read-only lookup with fully described parameters and safety annotations, the description supplies enough context to understand what the tool returns. It could be slightly stronger if it clarified the shape of the returned names, but the absence of an output schema makes that less critical.

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 parameter meanings are fully documented in the schema itself. The description mentions language and historic names, which aligns with two parameters, but it adds no extra syntax or behavioral detail beyond the schema.

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 clearly states that the tool retrieves all GeoNames names for a place, region, or country, including names by language and historic names. It identifies the resource and scope well, but it does not explicitly distinguish this tool from potentially overlapping siblings such as place_details or find_city.

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 description implies when to use it: looking up alternate-language names and historic names for a place. However, it gives no explicit when-not-to-use guidance and does not name an alternative tool for cases where broader place details are needed.

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