Crawlora MCP

wolt_restaurant_menu_search

Read-only

Search one Wolt restaurant's or store's own items by keyword, with name, description, price, dietary tags, image, and -- for packaged retail products -- barcode, pack size, and per-unit price. The only way to reach a large grocery or retail store's items, since wolt_restaurant_menu returns those venues' categories without items. Matches across languages.

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>",
      "query": "<query>"
    },
    "name": "wolt_restaurant_menu_search"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Wolt restaurant/store slug, from /wolt/search's slug field.
`limit`	No	Max items returned. Defaults to 30, maximum 100.
`query`	Yes	Keyword to match against this venue's own item names and descriptions (required). Wolt matches across languages, so an English keyword finds locally-named products.

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 5, 2026

TDQS

A4.4/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 value beyond that: it discloses the returned fields (dietary tags, barcode, pack size, per-unit price) and the cross-language matching behavior, which the agent couldn't infer from annotations alone.

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 the action and scope, and every clause carries operational information (fields, sibling routing, language matching). Slightly long but nothing is wasted.

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?

An output schema exists, yet the description still gives enough field-level context to know whether this tool answers a given question, and it resolves the key ambiguity (grocery/retail venues) against the sibling. Nothing needed to invoke it correctly 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 slug, limit, and query are already documented in the schema. The description adds only the cross-language matching nuance for the keyword; it says nothing extra about slug or limit. Baseline 3 is appropriate.

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 (search) acting on a specific scope (one Wolt restaurant's or store's own items) by keyword, and enumerates the returned fields. It explicitly differentiates itself from the sibling wolt_restaurant_menu, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (wolt_restaurant_menu) and the exact condition that selects this tool instead: grocery/retail venues whose categories come back without items. It also states this is the only route to those venues' items, which is decisive 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?