Skip to main content
Glama

List cities with deals

list_cities
Read-onlyIdempotent

List the cities that currently have one-way campervan relocation deals starting or ending there, with coordinates, deal counts and providers. Optionally count only deals that overlap a travel window or come from given providers. Use it to find the exact city names search_deals accepts, or the nearest city with deals to a place that has none. Read-only.

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_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast day of the travel window, YYYY-MM-DD. Keeps deals whose own window starts on or before it.
providersNoOnly these providers: roadsurfer (Roadsurfer), indiecampers (IndyCampers), imoova (Imoova). Leave out for all three.
start_dateNoFirst day of the travel window, YYYY-MM-DD. Keeps deals whose own window ends on or after it.

Output Schema

NameRequiredDescriptionDefault
totalYesCities in this answer.
citiesYes

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and a closed-world scope, so the trailing 'Read-only' is partly redundant. The description still adds real behavior: only 'currently' active deals are listed, provider filtering defaults to all three, and date filters narrow counts by overlap rather than by exact match. No pagination or result-size limits are mentioned.

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?

Two tight sentences, front-loaded with what is listed and followed by the filtering and routing guidance. Every clause carries information; nothing is padding.

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?

Output schema exists, so return structure need not be explained, yet the description still names the key returned fields. Filters, defaults, and the handoff to search_deals are all covered, which is complete for a zero-required-param read tool.

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 100%, so all three parameters are already fully documented with formats and semantics. The description only restates the optional-filter framing ('count only deals that overlap a travel window or come from given providers') without adding format or interaction detail beyond 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 ('List the cities') plus the qualifying scope ('that currently have one-way campervan relocation deals starting or ending there') and the payload (coordinates, deal counts, providers). It also differentiates from the sibling by positioning itself as the source of city names search_deals accepts.

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 two concrete use cases: resolving city names for search_deals, and finding the nearest city with deals when a place has none. The alternative (search_deals) is named with the condition that selects it, though no explicit when-not-to-use case is offered.

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