Crawlora MCP

wolt_search

Read-only

Wolt restaurant/store search near a coordinate, optionally filtered by a keyword or browsed by category (call wolt_search_filters for valid category values, wolt_cities for coordinates): slug, name, address, coordinates, tags, price range, rating, and delivery estimate, plus per-venue category ids on the browse modes. A keyword search also accepts sort, product_line, and open_now.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "wolt_search"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Optional result ordering for a keyword search. One of recommended, distance, rating, delivery_fee, delivery_estimate. Requires query.
`limit`	No	Max restaurants/stores returned. Defaults to 30, maximum 100.
`query`	No	Optional keyword to search restaurant/store names, dishes, or cuisines by. Omit for a plain location browse of nearby restaurants and stores. Cannot be combined with category.
`category`	No	Optional Wolt category id to browse by (e.g. pizza, sushi, vegan) instead of a keyword search -- call /wolt/search/filters for the current, complete, location-scoped list of valid values. Cannot be combined with query. An unrecognized value returns a 404.
`latitude`	Yes	Search center latitude (required).
`open_now`	No	When true, restrict a keyword search to venues currently delivering. Requires query.
`longitude`	Yes	Search center longitude (required).
`product_line`	No	Optional store-type filter for a keyword search. One of restaurant, grocery, alcohol, pharmacy, pet_supply, health_and_beauty, electronics, toys_games_and_kids, home_and_diy, florist, general_merchandise, gift_card, charity, subscription, other. Which of these a market actually stocks varies by country; a store type absent from the searched market returns no results rather than an error. Requires query.

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds mode-dependent behavior (per-venue category ids appear only on browse modes) but otherwise enumerates return fields that the output schema already provides, so incremental behavioral value is limited.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded with the core action and mode distinction, which is good, but the long return-field enumeration duplicates the output schema and pads the definition. The routing hints are useful; the field list is not earning its place.

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?

Given an output schema exists, the description needn't list return values, and the routing to sibling tools plus the mode constraints make it complete enough to call correctly. The main gap is that it doesn't clarify pagination/total behavior, but nothing critical 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 all eight parameters are documented in the schema, including the query/category mutual exclusion and the 'requires query' constraints. The description repeats these constraints (sort, product_line, open_now) rather than adding syntax or format detail beyond the schema, so 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+resource (Wolt restaurant/store search) and the key scoping input (near a coordinate), then distinguishes its two modes: keyword-filtered search vs category browse. An agent can tell it apart from wolt_search_filters and wolt_cities 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?

Explicitly routes the agent: call wolt_search_filters for valid category values and wolt_cities for coordinates, and notes sort/product_line/open_now apply only to keyword search. It stops short of stating when NOT to use it or naming the sibling search tool for other cases, but the conditional guidance is clear.

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.