Skip to main content
Glama

GeoLocale

Find cities on GeoLocale

find_cities
Read-only

List the cities GeoLocale covers, filtered by part of a city name and/or a country. Returns each city's id, its number of neighborhoods, how many have counts, the date of its map data and the address of its page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many cities to return. Default 25.
queryNoPart of a city name, for example "lisbon".
countryNoPart of a country name in English, for example "portugal".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value by enumerating the returned fields (id, neighborhood count, counted neighborhoods, map data date, page address) and clarifying that filters are substring matches, which is behavior the annotations do not convey.

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?

Two sentences, both front-loaded: the first defines the operation and filters, the second defines the return shape. Nothing is redundant with the schema.

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 correctly compensates by listing the returned fields, and the filters plus the schema-documented limit are sufficient to call it. Only ordering/pagination of results beyond the limit is left unspecified.

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 all three parameters are already documented with examples. The description adds only the 'and/or' combinability of query and country, which is a marginal gain over the schema; baseline 3 applies when the schema carries the detail.

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?

Names a specific verb (List) and resource (cities GeoLocale covers), and states the filtering scope. It does not explicitly contrast with the sibling tools, but the resource is unambiguous enough that an agent can separate it from compare_neighborhoods and neighborhood_facts.

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 phrase 'filtered by part of a city name and/or a country' implies when the tool is useful (looking up a city or a country's cities), but there is no explicit when-to-use vs when-not guidance and no named alternative. Usage is inferable rather than prescribed.

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