Skip to main content
Glama

uber_eats_guide

Guides AI agents through Uber Eats Manager screens to find stores, menus, hours, orders, and the sign-in link before starting tasks.

Instructions

How to work in Uber Eats (stores, menus, hours and orders): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Uber Eats, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does imply this is a safe informational lookup rather than an action. However, it never states explicitly that it is read-only/no side effects, nor does it describe the form of the guidance returned (documentation text vs. URLs vs. screen identifiers). It adds context but leaves the mutation-safety question to inference.

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?

Two short sentences, front-loaded scope before the ordering instruction, with zero filler. The parenthetical list is slightly clunky but earns its place by naming the covered domains.

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 guidance tool with no output schema, the description covers scope and ordering adequately, but the agent still cannot predict the response's shape or how large it will be. A clause on what it returns (e.g., screen map plus sign-in URL) would close the remaining gap.

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% with a single optional 'task' parameter that is already documented as 'What you want done in Uber Eats, in your words.' The description adds no meaning about how the task field shapes the returned guidance or whether it can be omitted safely, so the schema does all the work — baseline 3.

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?

The description states a specific resource — guidance for working in Uber Eats covering stores, menus, hours, orders, screens, and the sign-in link — and distinguishes itself from the sibling UI-action tools (open, click, type, read, status, close) by being the orientation/reference tool. 'How to work in' is slightly soft as a verb, but the enumerated coverage makes the purpose unambiguous.

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?

'Call this first' is explicit sequencing guidance that tells the agent to invoke it ahead of the sibling action tools, which is the key routing decision here. It gives no when-not conditions or mention of returning to it later, so it stops short of full 5-level guidance.

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