Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UE_LOCALENoInterface language for Uber Eats. Set to 'jp' for the Japanese interface. Default is 'en'.en
OPENCLI_BINNoPath to the opencli binary. Only needed if opencli is not located at ~/.npm-global/bin/opencli.~/.npm-global/bin/opencli

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ue_policyA

Read the ordering policy: whether ordering is enabled, per-order / per-day caps (in the account's currency), how much was already spent today, and whether the user is logged in to Uber Eats in Chrome.

Use this when:

  • You're about to add to cart or place an order — check the caps first.

ue_searchA

Search Uber Eats (delivers to the account's current address; works in any country Uber Eats serves). Works with store names, dishes and products. Product searches (e.g. 'Gatorade', 'ポカリスエット') return supermarkets / drugstores together with the matching items and prices.

Use this when:

  • The user asks for delivery ('点个 X' / 'order me X'). Delivery is real food and real money — don't start a delivery order on your own initiative.

ue_storeA

A store's menu: item ids, names, prices, sections, quick-add, sold out.

Notes:

  • Supermarkets / convenience stores / drugstores only show a few shelves on their front page — pass query to search inside the store. Their item ids are long (store:item:section:subsection); pass them to ue_add unchanged.

ue_addA

Add one item to the cart (a write action). spec = option keywords, space-separated, one per option group (e.g. 'Coke Large' / 'コーラ ポテト(L)'; multi-level options are matched level by level); qty = quantity 1-10. Confirm with ue_cart afterwards.

Notes:

  • Uber Eats keeps one cart per store; several carts can exist at once.

  • Adding is not buying. Confirm with the user before adding anything.

ue_cartA

List the carts (one per store): draft_id, store, items, most recently changed first.

Use this when:

  • You've just added something and want to confirm it landed, or need the draft_id for ue_review.

ue_reviewA

Checkout snapshot for one cart — the only trusted price: store / items / options / subtotal / every fee / total / ETA / delivery address / payment method. Read from Uber's checkout API keyed by draft (not the page), with two independent anchors that throw instead of mixing two carts. Returns a confirm_token (valid ~10 min, single use).

Use this when:

  • Before placing an order: show the user this exactly as returned; only after they say yes, call ue_place.

ue_placeA

Place the order. Requires the confirm_token from ue_review; the checkout snapshot is re-read and must still match (total / store / cart) and be within the per-order / per-day caps — otherwise it refuses.

Use this when:

  • The user has explicitly said yes to the exact review you showed them. Only then.

Notes:

  • If it comes back status unknown, or with any error after the gates passed, that does NOT mean it failed — the order may well have gone through. Check ue_orders first and tell the user what you find.

  • Never call ue_place again for the same cart: a second press is a second order and a second charge.

ue_ordersA

Active orders and delivery progress.

Use this when:

  • Right after ue_place, to confirm the order landed — always when ue_place came back unknown or with an error.

  • While the food is on the way, if the user asks where it is.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation5/5

Each tool maps to a distinct stage of the ordering workflow (policy, search, store, add, cart, review, place, orders) with no overlapping purposes. The descriptions reinforce the intended sequence, so an agent can reliably pick the right tool.

Naming Consistency4/5

All tools share a consistent 'ue_' prefix and single-token names, which is highly readable. It mixes nouns (ue_policy, ue_cart, ue_orders) and verbs (ue_search, ue_add, ue_place) rather than a strict verb_noun pattern, but the convention is still predictable.

Tool Count5/5

Eight tools map cleanly onto the browse → add → review → place → track lifecycle, with each tool earning its place. Nothing feels redundant or missing for the stated ordering purpose.

Completeness4/5

The core ordering lifecycle is fully covered with safety gates (policy, review, place, orders). Minor gaps exist: there is no way to remove/modify items from a cart, clear a cart, or cancel an order, which an agent cannot fully work around.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive