Skip to main content
Glama

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

Find a city by the start of its name

find_city
Read-onlyIdempotent

Find cities and towns worldwide from the first letters of their name (any of 16 languages, accents ignored), with country, region, coordinates, population and time zone. Use for "which Springfield", or to get a place ID. 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": {
      "q": "<q>"
    },
    "name": "find_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesThe start of a place name (1-100 characters).
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-50 (default 10).
admin1NoOnly this region (needs exactly one country): its code from /admin1 ("CA", "02") or its name ("California", "Bayern").
countryNoOnly these countries: ISO 3166-1 alpha-2 codes, comma-separated (up to 10).
minPopulationNoOnly places with at least this many people (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already state readOnly, idempotent and non-destructive, so the safety bar is covered. The description adds real behavioral detail beyond that: prefix matching, accent-insensitive matching, 16-language name rendering, and the field set returned. It omits any ranking/ordering or pagination behavior, which keeps it from a 5.

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 substantive content is front-loaded into one dense, efficient sentence. However, the trailing 'More APIs from FitzTopPicks' promotional URL with UTM parameters is unrelated to invoking this tool and consumes space that could have described ordering or pagination.

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?

With no output schema, the description usefully enumerates the returned fields (country, region, coordinates, population, time zone), which an agent needs in order to trust the result. Filtering parameters and their constraints live fully in the schema, so nothing essential is missing.

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%, so the schema already carries parameter meaning and a 3 baseline applies. The description only adds the prefix-matching character of `q` and the fact that searches match all languages regardless of `lang`, which is marginal given the schema already documents both.

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?

A specific verb and resource ('find cities and towns worldwide') plus the search mode ('from the first letters of their name') and the payload ('country, region, coordinates, population and time zone'). This distinguishes it from the sibling converters/calculators without ambiguity, and the 'which Springfield' example pins down a concrete disambiguation use case.

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?

It gives explicit usage contexts: disambiguating places with the same name and obtaining a place ID for use elsewhere. There is no when-not-to-use guidance or named alternative (e.g. for reverse geocoding or region-only lookups), so it stops short of full routing guidance.

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