CheapCarRent search

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

Name	Required	Description	Default
`query`	No
`country`	No
`airports_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent and non-destructive, so the safety profile is covered; the description adds genuinely new behavior: unknown country codes error out with the list of covered codes, empty result sets mean the destination is unsupported, and accents are ignored in matching. These are hiring-rule-style details an agent could not infer from the schema or annotations.

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 front-loaded sentences, the first of which establishes scope and value, followed by return fields, filtering, and the handoff to search_cars. The row-field enumeration is long but justified because no output schema exists; there is essentially no wasted wording.

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?

For a three-optional-parameter reference tool with no output schema, the description covers what is returned, how to filter, error behavior, and how to feed the result into a sibling tool. Nothing an agent needs in order to call it and interpret the response is missing.

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 description coverage is 0%, so the description must carry the parameter meaning and it largely does: country is a two-letter code, query matches city, country, alias or airport code with accents ignored, and airports_only restricts to airport rows. Only airports_only's exact semantics are left slightly implicit (only "filter with" names it), which keeps it off a 5.

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 ("List the cities and airports CheapCarRent search accepts") and adds a distinguishing qualifier ("with the exact spelling"). It also enumerates the returned fields, so an agent can tell at a glance this is a lookup/reference tool, not the actual car search that search_cars performs.

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 concrete downstream routing: "Pass countryCode as country and cityParam as city to search_cars, or pass iata", which tells the agent exactly what to do with results. It also covers the negative case (empty list = place not covered, do not guess another spelling). It stops short of explicitly saying this should be used before search_cars as a prerequisite, so a 4 rather than a 5.

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

All CheapCarRent search tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?