Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

glovo_store_fees

Retrieve a Glovo store's small-basket surcharge tiers, including basket-value ranges, extra fees, currencies, and strategy names, to see added charges on small orders.

Instructions

Get one Glovo store's small-basket surcharge tiers. Returns the small-basket surcharge tiers of one store: for each basket-value range (lower_bound to upper_bound) the extra fee charged, its currency and Glovo's strategy name. A store with no small-basket surcharge returns an empty tiers list. When address_id is omitted the store's own default location is looked up first, which costs one extra upstream call.

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_fees"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City slug (madrid) or city 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 /glovo/city's supported_languages.
`store_id`	Yes	Store id, from /glovo/stores' id field.
`address_id`	No	Optional store location id, from /glovo/stores' address_id field.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.1/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 disclosure burden and does reasonably well: it describes the return shape, the currency and strategy name fields, the empty-list case for stores without a surcharge, and the cost consequence of omitting address_id. It omits error conditions and rate/limit behavior, keeping it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences of appropriate length, front-loaded with purpose and ending with the cost caveat. The first two sentences overlap ("Get ... surcharge tiers" / "Returns the small-basket surcharge tiers of one store"), which is the only wasted space.

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?

No output schema exists, so the description correctly explains the returned structure and the empty-result case, and it covers the one non-obvious parameter behavior. Complete enough to call correctly; only failure handling is unaddressed.

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%, so a 3 is the baseline, but the description adds meaning the schema does not: it explains what happens when address_id is omitted (default location lookup at the cost of one extra upstream call). It adds nothing about country/city/language 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?

"Get one Glovo store's small-basket surcharge tiers" names a specific verb and a narrowly scoped resource, then immediately defines what a tier is (basket-value range plus extra fee). This is clearly distinct from store-detail or menu siblings such as glovo_store or glovo_store_menu.

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 implied by the narrow resource scope, and there is a useful conditional note about address_id omission, but the description never states when to prefer this tool over glovo_store or what to do if the store has no surcharges beyond inferring an empty list.

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

Deploy Server