Crawlora MCP

glovo_store_fees

Read-only

Return one Glovo store's small-basket surcharge tiers: each basket-value range with its extra fee, currency and strategy. An empty tiers list means no surcharge. Requires country, city and store_id from glovo_stores; pass address_id to skip an extra lookup.

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 code (mad), from /glovo/cities.
`country`	Yes	Two-letter country code, from /glovo/cities.
`language`	No	Optional two-letter response language; defaults to en.
`store_id`	Yes	Store id, from /glovo/stores' id field.
`address_id`	No	Optional store location id, from /glovo/stores' address_id field. When omitted the store's own default location is looked up first.

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 7, 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 real behavioral content beyond that: an empty tiers list is a meaningful negative result rather than an error, and omitting address_id triggers an additional lookup (latency/call cost). It doesn't discuss failure modes for an unknown store_id.

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 tight sentences, front-loaded with what is returned before the prerequisites. Minor redundancy with the output schema in the field enumeration, but nothing is wasted or buried.

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

Completeness5/5

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

For a single-store read lookup with a full schema and an existing output schema, the description covers the input provenance, the returned structure, and the empty-list edge case. There is nothing an agent needs in order to call it or interpret the result that 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 coverage is 100%, so every parameter including address_id and language is already documented in the schema. The description reinforces the required trio and the address_id shortcut but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 small-basket surcharge tiers') and enumerates the returned fields (basket-value range, extra fee, currency, strategy). This is clearly distinguishable from siblings like glovo_store, glovo_store_menu or glovo_store_products, which cover store metadata and products rather than fee tiers.

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 concrete prerequisites and provenance: country, city and store_id must come from glovo_stores, and address_id can be supplied to avoid an extra lookup. It does not name an explicit alternative tool or a 'use this instead when...' exclusion, so it stops 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?