Skip to main content
Glama
Sign In
@striderlabs/mcp-ubereats

@striderlabs/mcp-ubereats

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ubereats_checkout

Preview your Uber Eats order summary including items, fees, and delivery estimate. Set confirm to true to place the order after reviewing.

Instructions

Preview or place the order. Set confirm=false (default) to preview the order summary including items, fees, and estimated delivery. Set confirm=true to actually place the order. Always preview before placing.

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": {
      "confirm": "<confirm>"
    },
    "name": "ubereats_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet to true to place the order, false to preview only. Defaults to false for safety.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Describes the two behavioral modes (preview vs place) and the preview content, but does not cover edge cases like empty cart or order confirmation details. Acceptable given the simple parameter.

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 purpose, followed by usage instructions. No wasted words.

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?

Covers the core behavior and preview output, but lacks prerequisites (e.g., logged in, items in cart) and post-placement output. Still sufficiently complete for the tool's simplicity.

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

Parameters5/5

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

Adds significant value beyond the schema by explaining what preview shows (items, fees, estimated delivery) and reinforcing the safety default behavior.

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 previews or places an order, distinguishing it from sibling tools like ubereats_add_to_cart or ubereats_view_cart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to set confirm=false for preview and confirm=true for placement, with a safety directive to always preview before placing.

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

Deploy Server

Other Tools