Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ubereats_feed

Fetch restaurants delivering to a given latitude and longitude from UberEats, returning names, ratings, review counts, delivery estimates, cuisines, and cover images.

Instructions

Browse UberEats location feed. Returns restaurants delivering to a specific location: name, rating, review count, delivery estimate, cuisine tags, and cover image.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of restaurants to return, clamped to 50. Default 20
offsetNoResult offset for the location feed. Default 0
latitudeYesDelivery search center latitude
longitudeYesDelivery search center longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 burden. It usefully discloses the read-only nature and the exact return fields, but says nothing about pagination behavior (despite limit/offset params), rate limits, or auth requirements, so key operational context is missing.

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 efficient sentences with the purpose front-loaded before the return-field list. No filler, though the return-field enumeration could be trimmed since it borders on output-schema territory.

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?

With no output schema, the description compensates by naming the returned fields, and all four params are documented in the schema. The main gap is the absence of any pagination or usage caveat for a feed tool, but it is broadly complete for calling the tool 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 description coverage is 100%, so latitude, longitude, limit, and offset are already documented in the schema. The description adds only the framing that coordinates define a delivery search center and does not add syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 (Browse) and resource (UberEats location feed) plus what it returns, so an agent knows this yields a delivery-restaurant list for a coordinate. It does not explicitly distinguish itself from the sibling ubereats_search, leaving the feed-vs-search boundary to inference.

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 'delivering to a specific location' implies the use case (location-centric browsing), but there is no explicit when-to-use or when-not-to-use guidance and no mention of the sibling ubereats_search as an alternative. Usage is only implied.

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

Deploy Server

Other Tools