Skip to main content
Glama

uber_eats_read

Read the current Uber Eats page to extract its text and numbered buttons, links, and fields, optionally limited to a specific page element.

Instructions

Read the current Uber Eats page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the result includes page text, numbered buttons, links, and fields, and that it reads the current page, but it does not state whether the operation is strictly non-mutating, whether authentication is needed, or how much of a dynamic page is captured.

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?

The description is a single front-loaded sentence with no wasted wording. The colon-separated list efficiently states the returned artifacts.

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?

For a simple read tool with one optional parameter and no output schema, the description is largely complete because it explains what is read and what kinds of content are returned. It could still be improved by clarifying its relationship to sibling interaction tools, but nothing essential is missing for basic invocation.

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 description coverage is 100% for the single optional "element" parameter, so the schema already documents its meaning. The description adds no parameter-specific detail beyond the implicit page scope, which justifies the baseline score of 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 uses a specific verb, "Read," and names the resource, "the current Uber Eats page," then enumerates what is returned: text, numbered buttons, links, and fields. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as uber_eats_click or uber_eats_type.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives like uber_eats_click or uber_eats_type. The only usage cue is the implied notion that reading is used to inspect the page, with no when-not conditions or prerequisites stated.

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