Skip to main content
Glama

GeoLocale

Compare a city's neighborhoods

compare_neighborhoods
Read-only

Set the neighborhoods of one city side by side: the distance to the nearest rail or metro station, and how many parks, supermarkets, pharmacies, schools, restaurants and cafes lie within 1 km of each neighborhood centre. Counted from OpenStreetMap; the answer carries the date of the map data.

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": {
      "city": "<city>"
    },
    "name": "compare_neighborhoods"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, "name, country" when the name is shared, or GeoLocale's id for the city, for example "lisbon".
limitNoHow many neighborhoods to return. Default 30.
sort_byNoOrder by one measure: transit is closest station first, the others are most first. Omit for the order of the city page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / city / description
      Previous value: -"City name, \"name, country\" when the name is shared, or the id from find_cities."New value: +"City name, \"name, country\" when the name is shared, or GeoLocale's id for the city, for example \"lisbon\"."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only and not open-world. The description adds useful provenance and freshness context by stating the data is counted from OpenStreetMap and that the answer carries the map data date.

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 two sentences and front-loads the core operation and measures. The metric list is dense but necessary, and there is no filler wording.

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?

Because there is no output schema, the description must convey return content; it identifies the measures and the data date. It stops short of describing result structure, field names, and distance units, leaving minor gaps.

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 city, limit, and sort_by fully documented, so the baseline is 3. The description adds metric meaning such as the 1 km radius and neighborhood centre, but provides no parameter-specific syntax, defaults, or constraints beyond what the schema already supplies.

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?

States a specific comparison operation, 'Set the neighborhoods of one city side by side,' and enumerates the measures, making the resource and scope clear. It does not explicitly differentiate itself from sibling tools such as neighborhood_facts, so it falls short of a 5.

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 comparative framing implies when the tool is appropriate, but there is no explicit when-to-use versus when-not-to-use guidance or routing to alternatives. Guidance is therefore only implied.

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