Skip to main content
Glama

Find a city

find_city
Read-only

Search SmogRank's cities by name (local, old and short names too: "München", "Bombay", "NYC"), or find the nearest ones to a point. Returns each city's path for the other tools, whether it is measured by ground monitors (ranked) or only estimated from a model, and its page; a name search also returns the countries and regions it names, as places with their 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_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, with lon, instead of a name.
lonNo
limitNo
queryNoCity name, optionally with region or country: "Springfield, Illinois".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint=true/openWorldHint=false annotations, it discloses what comes back: the city path for other tools, whether the city is ground-monitor measured (ranked) or model-estimated, its page, and that name searches also return named countries and regions as places. That is meaningful behavioral context, though it omits what happens on empty results or how limit truncates output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two operational modes are front-loaded in the first clause, and examples are packed inline rather than expanded into their own sentences. The second sentence is long and semicolon-dependent, but every clause carries substantive information about return values.

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 takes on the burden of describing returns, and it does so thoroughly for both search modes. The remaining gap is that all four parameters are optional, yet the description never states that at least one of query or lat+lon must be supplied.

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

Parameters4/5

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

Schema coverage is 50% (lon and limit carry no textual description), so the description has to carry weight. It defines the query semantics well (local, old and short names with 'München', 'Bombay', 'NYC') and explains that lat/lon is the alternative 'to a point' path. The limit parameter and the consequences of exceeding it remain undocumented in both schema and description.

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 states a specific verb and resource ('Search SmogRank's cities') and immediately distinguishes its two modes: name lookup versus proximity search from a point. It also clarifies the tool's role as a discovery step that returns 'each city's path for the other tools', which separates it from siblings city_air, city_history and rankings.

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 clear context for use: search by name, or find nearest cities via a point, and subtly signals this is the entry point before calling the other tools. It stops short of explicit exclusions or stating what to do when no city matches, so it is clear but not exhaustive.

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