Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

glovo_store

Retrieves a Glovo store's public details by country, city, and store ID, including address, fees, rating, open status, and promotions; unknown IDs return 404.

Instructions

Get one Glovo store's detail. Returns one store's public detail: name, slug, category, address and coordinates, whether it is open and enabled, rating label and count, delivery and service fees, cuisine filters, promotions and its default address_id. An unknown store_id returns a 404.

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>",
      "store_id": "<store_id>"
    },
    "name": "glovo_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug (madrid) or city code (mad), from /glovo/cities.
countryYesTwo-letter country code, from /glovo/cities.
languageNoOptional two-letter response language; defaults to en. A city's supported languages are in /glovo/city's supported_languages.
store_idYesStore id, from /glovo/stores' id field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it enumerates the returned fields (name, slug, category, address, coordinates, open/enabled status, rating, fees, cuisines, promotions, default address_id) and discloses the 404 error for an unknown store_id. It omits auth requirements and any rate-limit or caching behavior, which keeps it below a 5.

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, purpose front-loaded, no filler. The long second sentence is a field inventory that substitutes for the absent output schema, so every clause earns its place.

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 four-parameter read tool with no annotations and no output schema, the description covers purpose, return contents and the key failure mode. Only ancillary behavior such as authentication or result freshness is unaddressed.

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 country, city, language and store_id are already documented in the schema with their source endpoints and formats. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Get one Glovo store's detail' — and immediately enumerates what that detail comprises, making it clearly distinct from the list-oriented glovo_stores sibling. It stops short of naming any sibling explicitly, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is only implied by 'one store's detail' — an agent can infer this is the single-record lookup versus a list call, but there is no explicit when-to-use, when-not-to-use, or named alternative. The only concrete routing hint is the 404 behavior for an unknown store_id.

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