Skip to main content
Glama

uber_eats_open

Open the Uber Eats merchant page in a signed-in cloud browser to inspect stores, menus, hours, and orders.

Instructions

Open a Uber Eats page in your signed-in Cloud Browser (default https://merchants.ubereats.com) to work with stores, menus, hours and orders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "uber_eats_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://merchants.ubereats.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/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 the full burden. It usefully signals that the browser is already authenticated ('your signed-in Cloud Browser') and gives the default URL, but says nothing about whether opening a page replaces the current one, loses unsaved state, waits for load, or fails on bad URLs.

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?

One compact sentence with the action and default front-loaded and no filler. Minor awkwardness in wording ('a Uber Eats') but nothing wasted.

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

Completeness3/5

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

For a one-parameter navigation tool with no output schema this is close to adequate, but it leaves sequencing relative to the click/read/type/close siblings and the state effect of navigating unaddressed, which an agent needs to compose a session correctly.

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 coverage is 100% and the single 'url' parameter already documents its default, so the description's mention of the default URL merely restates the schema. No additional meaning, such as accepted URL forms or whether external domains are allowed, is added.

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 ('Open') and resource ('a Uber Eats page') plus the environment ('signed-in Cloud Browser') and default location. It is clearly distinguishable from siblings like uber_eats_click, uber_eats_read, or uber_eats_status, though it does not explicitly name them.

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?

The phrase 'to work with stores, menus, hours and orders' implies this is the entry point that precedes read/click/type actions, but the definition never says when it must be used versus those siblings, nor whether it should be called once per session or per page.

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