Crawlora MCP

glovo_city

Read-only

Return one Glovo city's market settings: name, enabled flag, primary language, supported languages (the values of every glovo_* language parameter for that city), currency and timezone. Requires country and city from glovo_cities.

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>",
      "city": "<city>"
    },
    "name": "glovo_city"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City slug (madrid) or code (mad), from /glovo/cities.
`country`	Yes	Two-letter country code, from /glovo/cities.
`language`	No	Optional two-letter response language; defaults to en. A city's supported languages are in this endpoint's supported_languages.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.2/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 that this is a per-city settings lookup and explains that supported_languages are the values of the glovo_* language parameters for that city. It says nothing about missing-city behavior or error responses, keeping it out of the top band.

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, with the field list and the prerequisite front-loaded in that order. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read lookup with a full input schema and an output schema, this is essentially complete. The field enumeration slightly duplicates the output schema, and there is no note on what happens for an unknown city, but no critical information for calling it correctly 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%, including where city/country values come from and that language defaults to en, so the schema already carries the parameter semantics. The description restates the provenance of country and city without adding format, case, or fallback details 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?

The description gives a specific verb and resource ('Return one Glovo city's market settings') and enumerates the exact fields returned: name, enabled flag, primary language, supported languages, currency, timezone. It is clearly distinct from the sibling glovo_cities, which it names as the source of the identifiers.

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?

It establishes the prerequisite explicitly ('Requires country and city from glovo_cities'), which tells an agent to call the list endpoint first rather than guessing slugs. It does not spell out when NOT to use this tool or contrast it with glovo_stores, so it falls short of full routing guidance.

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

All Crawlora MCP tools Inspect

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

Need Help?