Skip to main content
Glama

List cities

list_cities
Read-onlyIdempotent

List the cities of a country that have active listings, busiest first. Returns each city's slug, name, state or province, escort and venue counts and its escortfox.com link. Use the city slug as city in search_listings, and the city's region as country where it differs from the country code (US states, e.g. "US-CA").

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": {
      "country": "<country>"
    },
    "name": "list_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesThe country whose cities to list: its `code` from list_countries (e.g. "DE"), or a region code such as "US-CA" for one state only.

Output Schema

NameRequiredDescriptionDefault
citiesYesCities with active listings, busiest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Required. ISO 3166-1 alpha-2 country code (e.g. \"DE\"), or a city's region code where the site splits a country by state (e.g. \"US-CA\"). Get valid values from list_countries / list_cities."New value: +"The country whose cities to list: its `code` from list_countries (e.g. \"DE\"), or a region code such as \"US-CA\" for one state only."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "cities": {
      +      "description": "Cities with active listings, busiest first.",
      +      "items": {
      +        "properties": {
      +          "country": {
      +            "description": "Country code.",
      +            "type": "string"
      +          },
      +          "escortCount": {
      +            "description": "Active escort listings.",
      +            "type": "integer"
      +          },
      +          "name": {
      +            "description": "City name.",
      +            "type": "string"
      +          },
      +          "region": {
      +            "description": "Country or region code, for `country`.",
      +            "type": "string"
      +          },
      +          "slug": {
      +            "description": "City slug, for `city`.",
      +            "type": "string"
      +          },
      +          "subdivision": {
      +            "description": "State or province, where the site names one.",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "The city page on escortfox.com.",
      +            "type": "string"
      +          },
      +          "venueCount": {
      +            "description": "Active venue listings.",
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "name",
      +          "region"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "cities"
      +  ],
      +  "type": "object"
      +}
  2. 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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds behavior not in the annotations: only cities with active listings are returned, results are ordered busiest first, and each row carries counts and a link — meaningful disclosure about filtering and ordering. It does not discuss empty-result behavior or pagination.

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 tight sentences: purpose and ordering first, return shape second, chaining guidance last. No filler and nothing buried at the end that an agent needs up front.

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?

A one-parameter read tool with full schema coverage, an output schema, and complete annotations needs little else. The description covers scope, ordering, and how to reuse the output, leaving nothing an agent needs in order to call it correctly.

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 the schema description already spells out accepting a country `code` from list_countries or a region code like 'US-CA'. The description restates that same meaning plus a pointer to regional usage, adding only marginal interpretation. Baseline 3 is appropriate when the schema does the explanatory work.

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 of a country'), adds a scope qualifier ('that have active listings'), and specifies ordering ('busiest first'). This distinguishes it cleanly from list_countries and list_districts without the agent opening either schema.

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 explicit downstream usage: feed the returned slug into `city` for search_listings, and use the region code as `country` where it differs. That is genuine workflow guidance. It stops short of saying when to pick this over list_districts or when a country has no listings, so no exclusions are stated.

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