Skip to main content
Glama

uber_eats_type

Type text into a numbered field on the current Uber Eats page, enabling AI agents to fill merchant forms by entering values such as prices, hours, or item names.

Instructions

Type text into a numbered field on the current Uber Eats page.

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": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "uber_eats_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for what is effectively a UI mutation. It reveals the state dependency ("current page") but says nothing about whether existing text is replaced or appended, whether typing triggers blur/submit events, or how failures (stale element numbers) surface.

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?

One short sentence with the action and target front-loaded and no filler. Nothing needs trimming, though very little is offered.

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 simple two-parameter tool with full schema documentation and no output schema, the core information is present. However, with zero annotation coverage on an input-simulating action, the definition should say more about state requirements and text replacement behavior.

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 both parameters documented inline including the minimum on "element" and its link to the last read. The description adds only the framing that the target is a numbered field on the current page, which is consistent with rather than additive to the schema.

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 names a specific verb ("Type") and a specific target ("a numbered field on the current Uber Eats page"), which cleanly separates it from siblings like uber_eats_click and uber_eats_read. It stops short of naming an alternative explicitly, but the action is unambiguous.

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 "on the current Uber Eats page" implies the page must already be open and that fields come from a prior read, matching the schema's "Field number from the last read." There is no explicit guidance on when to type versus click, or what to do if the element is not a text field, so the guidance is only implied.

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