Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

wolt_restaurant_availability

Read-only

Wolt restaurant/store live availability by slug: open/closed now, next open and close times, delivery and pickup estimates in minutes, delivery fee, order minimum, distance, and current discount campaign labels. Pass latitude/longitude to resolve delivery availability and a distance-scaled fee for that address.

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_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesWolt restaurant/store slug, from /wolt/search's slug field.
latitudeNoOptional delivery-address latitude. Wolt resolves delivery availability, delivery fee, delivery estimate, and distance against this coordinate; omit both to get the venue's generic, location-independent status.
longitudeNoOptional delivery-address longitude. Must be given together with latitude.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description goes further by disclosing that fees are distance-scaled and that omitting coordinates yields location-independent status. It stays silent on auth and rate limits, but adds real behavioral value beyond the annotations.

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 front-loaded sentences with no filler; the purpose and key output fields lead, followed by the coordinate behavior. The return-field enumeration is dense but each item aids tool selection, though it partly overlaps the existing output schema.

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?

With an output schema, 100% schema coverage, and annotations already present, the description only needs to frame purpose and conditional behavior, which it does. The one gap is the absence of alternative-tool routing among the many wolt siblings.

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%, so the baseline is 3. The description's note about latitude/longitude driving delivery availability and scaled fees largely restates what the schema parameter descriptions already say, adding little new semantic detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: 'Wolt restaurant/store live availability by slug', then enumerates the exact data returned (open/closed, next open/close, delivery/pickup estimates, fee, minimum, distance, discounts). An agent can tell it is an availability lookup, but it never names a sibling (e.g. wolt_restaurant for static details) to sharpen the distinction.

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?

Gives conditional guidance on the optional coordinates ('Pass latitude/longitude to resolve delivery availability and a distance-scaled fee'), which implies when to supply them, but offers no explicit when-to-use-this-vs-alternative routing among the many sibling tools (wolt_restaurant, wolt_search, wolt_restaurant_menu).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
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