@striderlabs/mcp-ubereats

ubereats_get_restaurant

Fetch full restaurant info including rating, delivery time, and fees, plus the complete menu organized by category, by providing a restaurant ID.

Instructions

Get full details and menu for a specific restaurant. Returns restaurant info (rating, delivery time, fees) and the complete menu organized by category.

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": {
      "restaurantId": "<restaurantId>"
    },
    "name": "ubereats_get_restaurant"
  }
}

Input Schema

Name	Required	Description	Default
`restaurantId`	Yes	The restaurant ID or slug (from ubereats_search results)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It lists returned data but does not explicitly state read-only nature, side effects, or requirements (e.g., auth). The read-only implication is clear but not spelled out.

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 fluff. Key information is front-loaded: action and resource first, then details of returns. Every sentence contributes meaning.

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 simple one-parameter tool with no output schema, description adequately covers return (restaurant info and menu). Lacks details on format or pagination, but sufficient for basic usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the parameter description adds value by specifying 'from ubereats_search results', providing source context beyond the schema's basic description.

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?

The description clearly states 'Get full details and menu for a specific restaurant' with specific verb 'Get' and resource 'restaurant'. It differentiates from sibling tools like ubereats_search (which searches) and ubereats_view_cart (cart-related), establishing a unique purpose.

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?

The description explains the tool's output (restaurant info, menu) and implies usage after obtaining a restaurant ID from search, but lacks explicit when-not-to-use or alternative tool guidance.

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

Deploy Server