APIbase

GeoNames Place Search

geonames.place.search

Read-onlyIdempotent

Search 12M+ global geographical places by name, country, feature type, or code to retrieve coordinates, population, and location details.

Instructions

Search the GeoNames geographical database for places, populated areas, mountains, rivers, and 12M+ geographical features worldwide. Filter by country (ISO-3166 2-letter code), feature class (A=administrative, P=populated place, T=mountain, H=water body, S=building/spot), and feature code (e.g. PPLC=capital, MT=mountain, STM=stream). Results include geoname_id, lat/lng, country, admin1/admin2, population, and Wikipedia link. Order by relevance (default), population, elevation, or Wikipedia linkage. Supports multilingual name lookup via lang parameter. CC BY 4.0 open data, no upstream cost.

Input Schema

Name	Required	Description
`q`	No	Full-text search query across place names, alternate names, and feature codes (e.g. "Paris", "Mont Blanc")
`name`	No	Search by exact or partial official place name (more precise than q; e.g. "New York")
`country`	No	Filter results to this ISO-3166 2-letter country code (e.g. "US", "FR", "DE")
`language`	No	ISO 639-1 language code for localized names in the response (e.g. "en", "fr", "de")
`max_rows`	No	Maximum number of results to return (default 10, max 1000)
`order_by`	No	Sort order: "relevance" (default, best name match), "population" (largest first), "elevation" (highest first), "wikipedia" (most linked)
`start_row`	No	Zero-based offset for pagination (default 0)
`feature_code`	No	GeoNames feature code for fine-grained filtering (e.g. "PPLC"=capital, "MT"=mountain, "STM"=stream)
`feature_class`	No	GeoNames feature class: A=administrative, H=hydrographic, L=parks/area, P=populated place, R=road, S=spot/building, T=mountain/hill, U=undersea, V=vegetation

Output Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
`result`	No	Tool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.2.0Oct 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds valuable context: licensing (CC BY 4.0), no upstream cost, ordering behavior (relevance default, population, elevation, Wikipedia), and multilingual lookup support. This goes beyond annotations without contradicting them.

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 moderately long but every sentence adds value: scope, filtering, result fields, ordering, language support, and licensing. It is front-loaded with the primary purpose, then systematically covers parameters and output. No filler or redundancy.

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?

For a 9-parameter search tool with a rich schema and output schema, the description covers all essential behavioral aspects: search scope, filtering options, ordering, result fields, language support, and licensing. Pagination is handled by schema parameters (start_row, max_rows). The agent has everything needed to select and call the tool correctly.

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 baseline is 3. The description restates parameter meanings (e.g., feature class codes, feature code examples, order_by options) that are already in the schema, adding little new information. It does not compensate for any schema gaps because none exist; it merely reinforces what the schema states.

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 states a specific verb ('Search') and resource ('GeoNames geographical database'), enumerates the types of features covered (places, populated areas, mountains, rivers, 12M+ features), and clarifies global scope. This clearly distinguishes it from sibling geocoding tools like nominatim.geocode.search or geo.places.search, even without naming them.

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 explains what the tool does and lists filtering options, but it does not explicitly state when to use this tool over alternative geocoding or place-search tools. No conditions, exclusions, or sibling comparisons are provided, leaving the agent to infer usage from the domain.

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

Deploy Server