Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

glovo_cities

List every country and city Glovo delivers in, returning each city's slug and code for use with other Glovo endpoints. Optionally filter by a two-letter country code.

Instructions

List the countries and cities Glovo serves. Returns Glovo's live directory of every country and city it delivers in, read from the directory its own landing page embeds. Each city carries the slug and the city code; every other Glovo endpoint takes country plus city (either the slug or the code) from here. The countries field always lists every supported country code, so the optional country filter's value space is discoverable; a country Glovo does not serve returns a 400 rather than an empty list. As of 2026-11-02 the directory covers 24 countries and 1,330 cities.

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

Input Schema

NameRequiredDescriptionDefault
countryNoOptional two-letter country code to restrict the directory to, e.g. es, it, pl. Omit for every country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so: it discloses the data source (Glovo's live landing-page directory), the per-city payload fields (slug and city code), the guarantee that the countries field enumerates the full filter value space, and the error semantics (an unsupported country returns 400 instead of an empty list). It also gives a dated coverage figure (24 countries, 1,330 cities) so an agent can judge result magnitude and freshness.

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?

Four sentences, each carrying distinct information, with the core purpose front-loaded and the workflow prerequisite second. Slightly dense in the middle (slug/code and countries-field guarantees could be tightened), but nothing is redundant.

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?

No output schema exists, so the description must explain return values, and it does: countries list plus per-city slug and code. For a one-parameter read tool with no annotations this is fully sufficient; the only quibble is the oddly future-dated freshness stamp (2026-11-02), which slightly undercuts the coverage claim.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline would be 3, but the description adds real meaning: it explains that the filter's value space is discoverable from the returned countries field, and that an out-of-range value is a 400 rather than an empty result. That is exactly the guidance an agent needs before passing a country code.

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?

A specific verb and resource: 'List the countries and cities Glovo serves', plus the clarifying detail that it is a live directory read from the landing page Glovo embeds. It is clearly distinguishable from the sibling city/store endpoints, which take their country and city inputs from this list.

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?

The description states the tool's role in the workflow: 'every other Glovo endpoint takes country plus city (either the slug or the code) from here', so calling it first is clearly implied. It also explains when to use the optional country filter versus omitting it. It never names a sibling (such as glovo_city) for single-city lookups or any explicit exclusion, so it stops short of a full when/when-not statement.

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

Deploy Server

Other Tools