Crawlora MCP

wolt_restaurant_menu

Read-only

Wolt restaurant/store menu grouped into categories, with name, description, price, dietary tags, and image per item. The loading_strategy field says whether the items are included: full means every category carries its items, partial means Wolt does not bulk-load this venue's assortment, so its categories come back with empty item lists and its items are reachable only through wolt_restaurant_menu_search. Large stores of any type -- supermarkets, pharmacies, drugstores, DIY and toy stores -- are commonly partial.

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": {
      "slug": "<slug>"
    },
    "name": "wolt_restaurant_menu"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Wolt restaurant/store slug, from /wolt/search's slug field.

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.

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the critical disclosure that partial venues return categories with empty item lists and that those items are only reachable through wolt_restaurant_menu_search. That is meaningful behavioral context an agent would otherwise have to discover empirically.

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 dense sentences, front-loaded with what is returned, then the loading_strategy caveat. The second sentence is long but every clause carries load-bearing information. No filler.

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?

An output schema exists, so return-value details need not be repeated in prose, and annotations cover the safety profile. The description nevertheless supplies the essential loading_strategy interpretation needed to use the tool correctly. Slightly incomplete on prerequisite context (how to get a valid slug), but overall adequate.

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?

There is a single parameter (slug) with 100% schema description coverage pointing back to /wolt/search. The description adds nothing about the slug format or how to obtain it, so the schema does the work; baseline 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?

Names a specific resource (Wolt restaurant/store menu) and its structure (categories with name, description, price, dietary tags, image), and explicitly distinguishes its behavior from the sibling wolt_restaurant_menu_search. An agent can tell it apart from other wolt_* tools without opening a schema.

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?

Clearly states the condition under which this tool is insufficient for retrieving items (partial venues) and routes the agent to wolt_restaurant_menu_search. It does not explicitly cover the full-range of alternatives (e.g., wolt_restaurant for metadata), but the primary routing decision is well defined.

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.