Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

glovo_stores

Read-only

List the first page of up to 50 Glovo stores in a city's category in Glovo's own ranking, optionally narrowed by filter_id, with total_entries for the whole category. Each store returns id and address_id for glovo_store, glovo_store_menu and glovo_store_products, plus rating, delivery estimate, fee and promotions. Only the first page is reachable anonymously; use filter_id to reach other subsets.

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>",
      "category_id": "<category_id>"
    },
    "name": "glovo_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug (madrid) or code (mad), from /glovo/cities.
limitNoMax stores returned from the page. Defaults to 50, maximum 50: Glovo's server-rendered list is one page of 50.
countryYesTwo-letter country code, from /glovo/cities.
languageNoOptional two-letter response language; defaults to en.
filter_idNoOptional cuisine or type filter id, from /glovo/stores/filters for the same category.
category_idYesStore category id, from /glovo/categories.

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.1/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. Beyond that, the description discloses non-obvious behavior: server-rendered single page of 50, anonymous access limited to page one, ranking order, and total_entries covering the whole category rather than the returned page.

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?

Three sentences, front-loaded with the scope and the page-size ceiling before the access caveat. Slightly dense but no filler; the return-field enumeration is the only part that partly duplicates the output schema.

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?

Given an output schema exists, the description does not need to enumerate return fields, yet it does so usefully to hint the chaining to glovo_store calls. Prerequisite lookups (cities, categories, filters) live in the schema, so an agent has everything required 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 description coverage is 100%, so all six parameters are already documented with provenance (cities, categories, filters endpoints). The description only adds a nuance for filter_id as the way to reach other subsets; otherwise it restates what the schema already carries.

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 ... Glovo stores') scoped to a city category, in Glovo's own ranking, and implicitly separates itself from the detail siblings glovo_store / glovo_store_menu by saying which ids it yields for those calls. An agent can route correctly without opening a 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 the key selection constraint ('only the first page is reachable anonymously; use filter_id to reach other subsets'), which tells the agent how to work around the hard 50-item ceiling. It does not explicitly name when to prefer glovo_store or glovo_stores_filters, though the return-field sentence effectively signals the drill-down path.

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