@striderlabs/mcp-ubereats

ubereats_add_to_cart

Add a menu item to your cart with quantity and special instructions after loading the restaurant.

Instructions

Add a menu item to the cart. The restaurant must be loaded first via ubereats_get_restaurant. Supports quantity and special instructions.

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>",
      "itemName": "<itemName>"
    },
    "name": "ubereats_add_to_cart"
  }
}

Input Schema

Name	Required	Description
`restaurantId`	Yes	The restaurant ID (from search or get_restaurant)
`itemName`	Yes	Name of the menu item to add (must match exactly)
`quantity`	No	Number of items to add (default: 1)
`specialInstructions`	No	Special preparation instructions for the item (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool adds to cart and supports quantity/special instructions, but omits key behavioral details: whether duplicate items increment quantity or replace, if a cart must exist, or login requirements. The mutation behavior is under-described.

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, front-loaded with the primary action, followed by a concise prerequisite and capability mention. No extraneous words; every sentence earns its place. Ideal for quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 4 parameters, no output schema, and no annotations. The description lacks crucial context: what happens on success (e.g., updated cart contents), error cases (item not found, invalid restaurant), or how the cart state evolves. Incomplete for a mutation tool.

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?

With 100% schema description coverage, the baseline is 3. The tool's description merely restates what the schema already provides (e.g., 'Supports quantity and special instructions'). It adds no new semantic value beyond the schema's detailed parameter descriptions.

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 the tool's action ('Add a menu item to the cart') with a specific verb and resource. It distinguishes from sibling tools like ubereats_view_cart and ubereats_clear_cart by explicitly adding items. The prerequisite reference to ubereats_get_restaurant further clarifies scope.

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 provides a clear usage context: the restaurant must be loaded first via ubereats_get_restaurant. This is an explicit prerequisite. While it doesn't list when not to use or alternatives, the given guidance is sufficient for a simple add-to-cart tool.

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

Deploy Server