Skip to main content
Glama

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

One place by its GeoNames ID

place_details
Read-onlyIdempotent

Everything about one place by its GeoNames ID (from find_city or places_near): names in 16 languages, region, country, coordinates, population, elevation and its time zone with the current UTC offset. 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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoShow names in this language (place, region and country): ar, de, en, es, fr, hi, it, ja, ko, nl, pl, pt, ru, tr, uk or zh ("en-US" works too). Without it, places carry GeoNames' own name (usually the local or international one). Searching always matches every language.
geonameIdYesThe GeoNames ID (geonameId in every result).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the bar is lower, and the description still adds concrete return scope: names in 16 languages, region, country, coordinates, population, elevation, and a time zone with the current UTC offset. It does not mention cost, rate limits, or error behavior for an invalid ID.

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 sentence is dense and front-loaded with the identity and the maximum payload. The trailing 'More APIs from FitzTopPicks' sentence with a UTM-tagged URL is pure promotion and does nothing to help tool selection.

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?

There is no output schema, so the description must carry the return-value burden, and it does so by enumerating the fields returned and the language coverage. Combined with a fully documented two-parameter schema, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by identifying find_city and places_near as the sources of the geonameId value. The lang parameter is left entirely to the schema, which already documents its enum and default behavior.

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 and resource ('everything about one place by its GeoNames ID') and enumerates the payload, so an agent can tell it apart from find_city and places_near at a glance.

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 parenthetical '(from find_city or places_near)' effectively tells the agent this is a follow-up lookup that consumes an ID returned by those siblings. There is no explicit exclusion statement or note about when not to use it, which keeps it below a 5.

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