Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

deliveroo_restaurant

Fetch any Deliveroo partner's details (restaurant, grocery, or shop) by its uname, including address, branch type, ratings, review count, and current order acceptance.

Instructions

Get one Deliveroo restaurant, grocery, or shopping partner's detail. Returns one Deliveroo partner's detail by uname -- restaurant, grocery, or shopping store alike, distinguished by branch_type: name, address, currency, branch/fulfillment type, rating, review count, a hero image, and whether it currently accepts orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unameYesRestaurant slug, from a search response's uname field
marketNoDeliveroo national market the uname was found in (default uk)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / market / enum
      Added value: +[
+  "uk",
+  "ie",
+  "fr",
+  "it",
+  "be",
+  "ae",
+  "kw"
+]
  2. Addedv1.16.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden; it clearly presents the operation as read-only ('Get', 'Returns') and discloses output traits including branch_type and live order-acceptance status. It doesn't discuss errors or availability, but for a simple detail lookup the behavior is sufficiently transparent.

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 with the core action and resource front-loaded, and the second sentence earns its place by enumerating return fields. There is slight redundancy between 'Get one... detail' and 'Returns one... detail'.

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 two schema-documented parameters, the description plus schema covers selection and expected return values. The absence of an output schema is mitigated by the field list; a minor gap is not explicitly routing to the menu tool, though the sibling name makes it inferable.

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%, with uname and market already documented including the default market, so the description doesn't need to add parameter detail. The description only repeats 'by uname' and adds no semantics 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?

The description states a specific action ('Get one... detail') and resource ('Deliveroo restaurant, grocery, or shopping partner'), distinguishing it from list/search and menu siblings. It also enumerates the returned fields, so an agent knows exactly what this tool provides beyond the tool name.

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 context is only implied: 'by uname' plus the schema note that uname comes from a search response. The description never names alternatives like deliveroo_restaurant_menu or deliveroo_search, and gives no when-not-to-use guidance.

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