Skip to main content
Glama

List cities and airports

list_locations
Read-onlyIdempotent

List the cities and airports CheapCarRent search accepts, with the exact spelling. Each row has country, countryCode, city, cityParam, iata when there is an airport, hasAirport, alsoAccepted spellings and the city page URL. Filter with country (two-letter code), query (city, country, alias or airport code; accents ignored) and airports_only. Pass countryCode as country and cityParam as city to search_cars, or pass iata. An unknown country code returns an error with the covered country codes. An empty list for a query means the place is not covered; do not guess another spelling.

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

Input Schema

NameRequiredDescriptionDefault
queryNoCity, country, alternative spelling or airport code to look for, e.g. Malaga or AGP. Accents are ignored; exact matches come first.
countryNoTwo-letter country code, e.g. ES or GR. Only places in this country are listed.
airports_onlyNotrue to list only places with an airport (rows that have an iata code).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / airports_only / description
      Added value: +"true to list only places with an airport (rows that have an iata code)."
    • addedInput schema / properties / country / description
      Added value: +"Two-letter country code, e.g. ES or GR. Only places in this country are listed."
    • addedInput schema / properties / query / description
      Added value: +"City, country, alternative spelling or airport code to look for, e.g. Malaga or AGP. Accents are ignored; exact matches come first."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds behavior well beyond that: accent-insensitive matching with exact matches ranked first, an error response carrying the covered country codes, and an explicit warning against fabricating alternate spellings on an empty result.

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?

Front-loaded with the core purpose, then the row shape, then filtering, then the handoff to search_cars. Every sentence is actionable, though the long run-on enumeration of row fields is dense and would read better as a compact list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description takes on the burden of describing the returned row fields — country, countryCode, city, cityParam, iata, hasAirport, alsoAccepted and the city page URL — and it does so. Combined with the error and empty-result semantics, an agent has everything needed to call this and interpret the response correctly.

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 100%, so the baseline is 3, but the description still adds meaning: it clarifies that query matches city, country, alias or airport code with accents ignored, that country is a two-letter code, and it maps the returned countryCode/cityParam fields back onto the search_cars parameters. The airports_only semantics are largely restated from the schema.

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?

States a specific verb and resource — lists the cities and airports the search accepts, with exact spelling — and frames it as a reference lookup distinct from the sibling search_cars. An agent can immediately tell this is the enumeration tool rather than the booking/search tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: resolve a place here, then pass countryCode as country and cityParam as city to search_cars, or pass iata directly. It also covers the failure paths — unknown country code returns an error listing covered codes, and an empty query result means the place is not covered so the agent should not guess another spelling.

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