Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

glovo_cities

Read-only

Return the Glovo city directory: every country and city it delivers in, with each city's slug and city code. Use this first: every other glovo_* tool takes country plus city (slug or code) from here. Optionally pass a two-letter country to filter; the countries field always lists every supported country.

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.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-schema behavior: the response carries slug and city code, and the countries field stays complete even when the directory is filtered to one country.

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 short sentences, all earning their place: what it returns, how to use it in the workflow, and how the filter behaves. The critical "use this first" instruction is front-loaded.

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 zero-required-parameter directory endpoint with an output schema and read-only annotations, nothing an agent needs is missing. The description even surfaces the fields the agent will reuse downstream (slug and city code).

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 coverage is 100% and the single country parameter is already documented with examples, so baseline is 3. The description adds meaning beyond the schema by clarifying that filtering narrows the directory but never narrows the countries list, which is a non-obvious semantic.

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?

"Return the Glovo city directory: every country and city it delivers in, with each city's slug and city code" names a specific verb, resource, and payload, and it is immediately distinguishable from siblings like glovo_city or glovo_stores.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this first: every other glovo_* tool takes country plus city (slug or code) from here" states an explicit ordering/dependency relative to the other Glovo tools, and the optional-filter sentence tells the agent when to pass country and when to omit it.

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

All Crawlora MCP toolsInspect
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