Skip to main content
Glama

List cities

list_cities
Read-onlyIdempotent

List the cities that have published restaurants and bars. A city can also be a travel destination, such as Los Cabos: search_venues finds its venues, and destination_overview and destination_listings read the destination's own board.

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
limitNoMaximum number of items to return.
cursorNoNumber of items to skip; pass `next_cursor` from the previous page.

Output Schema

NameRequiredDescriptionDefault
itemNo
itemsNo
reasonNo
sampleNo
sourceNo
statusYes
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / item / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / item / default
      Removed value: -null
    • removedOutput schema / properties / item / title
      Removed value: -"Item"
    • addedOutput schema / properties / item / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • removedOutput schema / properties / items / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "additionalProperties": true,
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / items / default
      Removed value: -null
    • removedOutput schema / properties / items / title
      Removed value: -"Items"
    • addedOutput schema / properties / items / type
      Added value: +[
      +  "array",
      +  "null"
      +]
    • removedOutput schema / properties / pagination / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": false,
      -    "description": "The page a paginated read actually served (FR-13, INV-8).\n\n``next_cursor`` is ``None`` both at the end of the results and when the next\ncursor would exceed ``max_public_cursor`` — in either case there is no\nfurther page a caller can legally request.",
      -    "properties": {
      -      "cursor": {
      -        "title": "Cursor",
      -        "type": "integer"
      -      },
      -      "limit": {
      -        "title": "Limit",
      -        "type": "integer"
      -      },
      -      "next_cursor": {
      -        "anyOf": [
      -          {
      -            "type": "integer"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "default": null,
      -        "title": "Next Cursor"
      -      },
      -      "total": {
      -        "title": "Total",
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "limit",
      -      "cursor",
      -      "total"
      -    ],
      -    "title": "Pagination",
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / pagination / default
      Removed value: -null
    • addedOutput schema / properties / pagination / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • removedOutput schema / properties / reason / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / reason / default
      Removed value: -null
    • removedOutput schema / properties / reason / title
      Removed value: -"Reason"
    • addedOutput schema / properties / reason / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / sample / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / sample / default
      Removed value: -null
    • removedOutput schema / properties / sample / title
      Removed value: -"Sample"
    • addedOutput schema / properties / sample / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / source / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / source / description
      Removed value: -"FR-13: which approved revision an answer was read from, and how fresh.\n\n``source`` is ``approved-content-revision:<id>`` for every read that answers\nfrom one venue, and the literal ``directory`` for the two cross-venue reads,\nwhich have no single revision to cite."
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "approved_at": {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "null"
      -      }
      -    ],
      -    "default": null,
      -    "title": "Approved At"
      -  },
      -  "content_version": {
      -    "title": "Content Version",
      -    "type": "integer"
      -  },
      -  "powered_by": {
      -    "anyOf": [
      -      {
      -        "type": "string"
      -      },
      -      {
      -        "type": "null"
      -      }
      -    ],
      -    "default": null,
      -    "title": "Powered By"
      -  },
      -  "source": {
      -    "title": "Source",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / source / required
      Removed value: -[
      -  "content_version",
      -  "source"
      -]
    • removedOutput schema / properties / source / title
      Removed value: -"SourceReference"
    • removedOutput schema / properties / status / title
      Removed value: -"Status"
    • removedOutput schema / title
      Removed value: -"PublicResponse"
  2. Changed1 schema field changed
    • addedOutput schema / properties / sample
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Sample"
      +}
  3. 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 closed-world, so the safety profile is covered; the description adds the substantive constraint that only cities with published restaurants and bars appear, which explains why a city the agent expects may be absent. It does not discuss ordering or page-size behavior, but the schema carries pagination and an output schema exists.

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 sentences, zero filler. The core scope comes first and the disambiguation/routing follows, so an agent can stop reading after sentence one and still call it correctly.

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?

With rich annotations, a complete parameter schema and an output schema, the description only needs to justify the tool's scope and its boundary with the destination siblings — both are done. Nothing required for a correct call is missing.

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 limit and cursor are already fully documented in the schema, including the next_cursor pass-through semantics. The description adds nothing about these parameters, so the baseline 3 applies.

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 a qualifying scope: only cities with published restaurants and bars. It also disambiguates the resource against a confusable concept (a city can be a travel destination), which an agent could not infer from the name alone.

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?

Explicitly routes the destination-board case away to search_venues, destination_overview and destination_listings, which is real alternative-naming rather than vague guidance. It stops short of saying when to prefer browsing cities at all versus going straight to search, so no full when/when-not pair.

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