Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

doordash_explore

Fetch DoorDash nearby stores feed by latitude/longitude without a query or account. Returns location-based browse JSON.

Instructions

Get DoorDash nearby stores explore feed. Returns DoorDash's location-based "nearby stores" browse feed from the Android mobile guest experience. Unlike search or autocomplete, no search query is required. No DoorDash account or caller-supplied token is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesConsumer latitude
longitudeYesConsumer longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that no auth token is required and that the feed comes from the Android mobile guest experience. However, it omits potential behavioral details like rate limits, pagination behavior, or error handling, leaving some uncertainty.

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 three concise sentences, all of which add value. It front-loads the main purpose, then adds differentiating and auth-related information, with no fluff or repetition.

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?

With only two parameters and no output schema, the description explains the tool's purpose and prerequisites well. However, it does not describe the output format or any pagination/limitations, which would be helpful for a tool without an output schema. Still, it covers the essential context for a simple read-only feed.

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% with clear descriptions for latitude and longitude. The description adds only that it is 'location-based' but does not specify format, bounds, or other nuances. Per the baseline for high schema coverage, this is adequate but not enriched beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves DoorDash's location-based 'nearby stores' explore feed. It explicitly distinguishes itself from search and autocomplete by noting no search query is required, which helps the agent differentiate it from sibling tools like doordash_search and doordash_search_autocomplete.

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?

The description gives clear context: use this when you want the browse feed without a search query, and it also notes no account or token is needed. It does not explicitly mention when to avoid using it or name alternative tools, but the contrast with search/autocomplete provides sufficient usage guidance.

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