Crawlora MCP

ubereats_store_menu

Read-only

Fetch the full Uber Eats menu for a known store, including section and item records with descriptions, prices, and availability. Use ubereats_store for store details or ubereats_store_reviews for customer reviews.

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": {
      "storeUuid": "<storeUuid>"
    },
    "name": "ubereats_store_menu"
  }
}

Input Schema

Name	Required	Description	Default
`storeUuid`	Yes	UberEats store UUID, as returned by the search endpoint's storeUuid 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 5, 2026

TDQS

A4.2/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 adds useful context beyond that by describing the shape and scope of what is returned (full menu, section and item records, prices, availability). It stops short of noting pagination, caching, or locale/menu-availability caveats.

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

Conciseness5/5

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

Two sentences, no waste, and the primary purpose is front-loaded ahead of the sibling routing guidance. Every clause earns 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?

With an output schema present, return-value explanation is not required, and the description still summarizes content usefully. The single parameter is fully documented. It is complete enough to call correctly, with only minor missing edge-case context (e.g. behavior for stores without a menu).

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% for the single storeUuid parameter, which even documents that it comes from the search endpoint's storeUuid field. The description's 'known store' phrasing reinforces that an identifier is required but adds no syntax or format detail beyond the schema, so 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?

States a specific verb (Fetch) and resource (full Uber Eats menu) scoped to a 'known store', and enumerates the returned content (section and item records with descriptions, prices, availability). This clearly distinguishes it from the other ubereats_* siblings that fetch stores, reviews, or search results.

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 names two alternatives and the conditions that select them (ubereats_store for store details, ubereats_store_reviews for customer reviews). The 'known store' phrasing implies the required precondition of an already-resolved storeUuid, but there is no explicit statement of when NOT to use it (e.g. to discover stores, use search/feed).

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?