Skip to main content
Glama

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

Places near a point

places_near
Read-onlyIdempotent

Which cities and towns are near a latitude/longitude? Places within a radius, nearest first, with the distance in km. 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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "places_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, decimal degrees (-90 to 90).
lngYesLongitude, decimal degrees (-180 to 180).
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.
limitNoResults, 1-100 (default 20).
radiusNoRadius in km, 1-200 (default 25).
minPopulationNoOnly places with at least this many people (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 non-open-world behavior, so safety is covered. The description adds genuinely new behavioral detail beyond that: results are sorted nearest-first and each carries a distance in km, which tells the agent what the response shape looks like.

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 front-loaded and efficient, but it is immediately followed by a promotional line linking to an unrelated API catalog with UTM tracking. That sentence does not help an agent select or call the tool and dilutes an otherwise tight definition.

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 geo query with fully documented parameters and no output schema, the description covers intent, ordering, and the key returned value (distance in km). The remaining gap is only edge-case behavior such as empty results or whether the center point itself is included.

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 description coverage is 100%, with lat, lng, lang, limit, radius and minPopulation all documented inline including ranges and defaults. The description only reinforces the radius-as-km unit, so the schema is doing the heavy lifting and baseline 3 applies.

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 opens with a specific question naming the resource (cities and towns) and the search basis (latitude/longitude plus radius), and adds result ordering (nearest first) and distance units. It is clearly a proximity search rather than a name lookup, though it does not explicitly contrast with siblings like find_city or distance_between_points.

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?

Usage is implied by the phrasing: use it when you have a coordinate and want populated places nearby. There is no explicit when-not guidance, no mention of what to do if no places fall in the radius, and no pointer to an alternative tool for name-based lookups.

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