Skip to main content
Glama

Search cities

search_cities
Read-onlyIdempotent

Find cities already in the dataset (the snapshot and places fetched before) by name, alias or id, optionally within one country. Returns ids for the other tools, how many match and whether more do. This server holds Borgo's published cities; any other place needs the local server (npx -y @abcastor/borgo mcp) and its fetch_city.

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": "search_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10 for a query, 100 for the full list
queryYesName, alias or id; empty lists every city
countryNoISO alpha-2 filter

Output Schema

NameRequiredDescriptionDefault
totalYesCities that match
citiesYes
hasMoreYes
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety needs no restatement. The description adds real value by defining the searched corpus (the snapshot plus previously fetched places), disclosing truncation ('whether more do'), and drawing the server's data boundary. It omits any note on how limit interacts with that truncation beyond what the schema says.

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?

Three tight sentences ordered as capability, return shape, then scope boundary and escape hatch; nothing is padded. The npx command is dense but functional rather than noise.

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 three-parameter read-only lookup with full schema coverage and an output schema, this covers purpose, corpus, return semantics and the out-of-scope path. The only meaningful omission is an explicit hand-off statement to get_city once an id is returned.

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% and each parameter already carries a description, including the empty-query behavior and the default/maximum on limit. The description's 'optionally within one country' and 'by name, alias or id' restate schema content rather than extending it, so baseline 3 applies.

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?

Specific verb and resource ('Find cities already in the dataset') with the matching modes spelled out (name, alias or id) and an optional country narrowing. It also signals its downstream role ('Returns ids for the other tools'), which separates it from a detail-fetch tool, though it never names get_city directly for contrast.

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 a concrete routing rule: this server only covers Borgo's published cities, and any other place requires the local server via npx and its fetch_city. That is an explicit when-to-use-elsewhere condition. It does not state when to prefer this over sibling get_city for a place already found, leaving that step to inference.

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.