Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

glovo_store

Read-only

Return one Glovo store's public detail by store_id: name, category, address and coordinates, open and enabled flags, rating label and count, delivery and service fees, cuisine filters, promotions and default address_id. Requires country, city and store_id from glovo_stores.

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 code (mad), from /glovo/cities.
countryYesTwo-letter country code, from /glovo/cities.
languageNoOptional two-letter response language; defaults to en.
store_idYesStore id, from /glovo/stores' id field.

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

A3.9/5.0
Behavior3/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 the useful 'public detail' qualifier and a field inventory, but says nothing about failure behavior for invalid store_id, caching, or rate limits – and the field inventory largely duplicates the output schema.

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?

Two sentences, front-loaded with the tool's purpose and followed by the prerequisite. The long field inventory is slightly list-heavy but each item maps to real return data, so little is wasted.

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 single-record lookup with a full output schema and 100% parameter coverage, the description covers scope, identifier sourcing, and returned content. Missing only the discriminating guidance against the menu/products siblings, which an agent might otherwise need.

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 coverage is 100% and each parameter already names its source endpoint; the description only reiterates that country, city and store_id come from glovo_stores, with no added syntax or format guidance (e.g. slug vs code for city, or the optional language parameter). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Return one Glovo store's public detail by store_id') and implicitly distinguishes itself from sibling list/menu tools (glovo_stores, glovo_store_menu, glovo_store_products) by emphasizing the single-store detail scope. The field enumeration further pins down what this tool returns.

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?

Explicitly names the prerequisite source for identifiers ('Requires country, city and store_id from glovo_stores'), which routes the agent through the correct upstream call. It stops short of naming alternatives such as glovo_store_menu or glovo_store_products, so the when-not-to-use boundary is only implied.

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