Skip to main content
Glama

Location and Timezone MCP Server by RoxyAPI

Search cities worldwide - Geocoding autocomplete with coordinates and timezone

get_location_search
Read-only

Turn a place name into coordinates, an IANA timezone and a DST-aware UTC offset, across 235,000+ cities and towns in 240+ countries. Coverage reaches rural towns of a few hundred people and every administrative seat, so a birthplace outside a major metro resolves as reliably as a capital. Matching is case-insensitive, accent-insensitive and partial, so ber matches Berlin, Bern and Bergen, native scripts are transliterated, and historic names resolve to the current place, so bombay returns Mumbai and peking returns Beijing. Results are ordered by match quality first and population second, so an exactly named small town is never buried under a larger city that merely shares its opening letters. Built for birth chart location pickers, horoscope apps, event scheduling, and any feature that needs place-to-coordinates resolution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesPlace to search for, written the way a person would. Accepts a bare city (berlin), a city plus country (berlin germany), a comma-qualified place (richfield, utah), a fully qualified place (richfield, utah, united states), or a historic name (bombay, peking, constantinople). Commas are optional, and a qualifier the dataset spells differently, such as USA for United States, still resolves. Matched against city name, alternate names, state or province, and country. Add the state or country whenever the name is common, since that is what separates the six Springfields, and Richfield, Utah from Richfield, Minnesota.
limitNoMaximum items to return per page. Range: 1-50, default 10.
offsetNoNumber of items to skip for pagination. Default 0.
compactNoSet true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context: matching is case-insensitive, accent-insensitive, and partial; native scripts are transliterated; historic names resolve; results are ordered by match quality then population. This goes well beyond the structured annotations, providing a rich picture of expected behavior.

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 length-dense but every sentence serves a purpose: it front-loads the core action, then adds coverage details, matching rules, ordering logic, and target use cases. There is no filler or redundancy, making it appropriately sized for a tool with this complexity.

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?

Given the tool's search complexity and the absence of an output schema, the description covers the necessary ground: it states the output type (coordinates, timezone, offset), explains coverage breadth, matching behavior, and result ordering, and provides real-world examples. It does not need to explain return structure since that is not in scope; the description is complete for selecting and invoking the tool correctly.

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

Parameters5/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds significant value beyond the schema, especially for 'q' with detailed guidance on quoting, comma usage, geographic qualifiers, and examples like 'bombay returns Mumbai'. It also explains the interplay between the 'q' parameter and result disambiguation, which the schema alone doesn't convey.

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 opens with a specific verb+resource: 'Turn a place name into coordinates, an IANA timezone and a DST-aware UTC offset' and amplifies scope with '235,000+ cities and towns in 240+ countries.' This clearly distinguishes it from the sibling country-list tools, making the purpose 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 description states its intended use cases ('Built for birth chart location pickers, horoscope apps, event scheduling, and any feature that needs place-to-coordinates resolution') and implies when to use it. However, it does not explicitly mention when not to use it or name alternatives, though the sibling tools are about country lists, so the context is reasonably clear.

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.

TDQS

A4.1/5.0
Disambiguation3/5

The three tools serve distinct purposes (country list, city list, place search), but the name 'get_location_countries_iso2' misleadingly suggests it returns country details rather than cities, creating potential confusion with 'get_location_countries'.

Naming Consistency3/5

All tools share the 'get_location_' prefix, but the suffixes are inconsistent: one describes an action ('search') while two describe resources ('countries', 'countries_iso2'), and the latter does not match its actual output (cities).

Tool Count5/5

Three tools is well-scoped for a location/timezone resolution server, covering country discovery, city listing, and place search without redundancy.

Completeness4/5

The core workflow of place name to coordinates/timezone is covered (country → city → search), but there is no reverse geocoding from coordinates or a direct timezone lookup, leaving a minor gap.

Resources