Skip to main content
Glama
World Time MCP Server

World Time MCP Server

find_cities

Read-only

Resolve ambiguous city names by listing matching cities and their time zones, ordered by population. Use it to identify the correct location before time-zone lookups or comparisons.

Instructions

List cities matching a name, largest first, with their time zones.

Useful when a name is ambiguous (e.g. "Paris" or "Springfield").

Args: query: City name, optionally with a country or US state after a comma. limit: Maximum number of results (1-25).

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": {
      "query": "<query>"
    },
    "name": "find_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 usefully adds result ordering and the presence of time zones. However, it never says how 'matching' works (exact, prefix, or fuzzy), which is the single most consequential behavior for a lookup tool, nor whether the limit truncates silently.

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?

Three short blocks — purpose, usage trigger, and an Args section — with zero filler and the core behavior front-loaded in the first sentence.

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 two-parameter read-only lookup with an output schema and annotations, the description covers purpose, ordering, returned field, and both parameter formats. The remaining gap is matching semantics, which materially affects how an agent should phrase the query.

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 0%, so the description must carry parameter meaning, and it does add real value: the 'name, country or state after a comma' syntax for query and the 1-25 bound for limit. But neither param is described as required, and it omits the default limit of 5, so compensation is partial rather than complete.

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 verb and resource ('List cities matching a name') and adds two concrete behavioral facts: results are ordered 'largest first' and each carries its time zone. The resource is plainly distinct from the time-conversion siblings, though the description never explicitly contrasts with them.

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?

Gives one clear when-to-use trigger: ambiguous names like 'Paris' or 'Springfield'. It does not name alternatives or say when not to use it (e.g. when a caller already has a resolved city ID), but the intended context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools