Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

doordash_store

Retrieve public DoorDash store metadata using numeric store ID and delivery coordinates. Get name, URL, images, ratings, and menu item counts.

Instructions

Get a DoorDash store. Returns public metadata for a DoorDash store by its numeric store_id, as seen from the delivery location given by the required latitude and longitude. The response has the name, URL, images, average rating, rating count, and menu section and item counts. Address, coordinates and price range appear only when DoorDash supplies them. Missing or out-of-range coordinates return 400.

Input Schema

NameRequiredDescriptionDefault
latitudeYesDelivery latitude
store_idYesNumeric DoorDash store ID
longitudeYesDelivery longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares the operation returns public metadata (read-only in effect), notes that address, coordinates and price range are conditional on DoorDash supply, and specifies that missing or out-of-range coordinates return 400. Auth/rate-limit context is absent, but the operational behavior is unusually well disclosed.

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?

Four sentences, front-loaded with purpose then response fields, then edge behavior. Each sentence carries distinct information, though the response-field enumeration is a dense list rather than strictly necessary prose.

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?

No output schema exists, so the description must explain returns, and it does (field list plus conditional fields). Error behavior is stated. For a three-parameter read tool this is close to complete, with only authentication or rate-limit context missing.

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 the schema already documents all three parameters. The description reinforces the key semantic that the coordinates are the delivery location from which the store is viewed, but adds no syntax, format, or range details beyond what the schema states.

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 concrete verb+resource ('Get a DoorDash store') and specifies exactly what it returns (name, URL, images, rating, counts). It does not, however, differentiate itself from close siblings like doordash_store_info or doordash_store_menu, so the agent must infer the split.

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?

Usage is implied by the required store_id plus delivery latitude/longitude, which tells the agent what inputs it needs. There is no explicit when-to-use versus doordash_store_info / doordash_store_menu / doordash_search, and no exclusions, leaving selection among near-identical siblings to inference.

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