Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

doordash_store_fulfillment

Fetch DoorDash store fulfillment options, delivery fees, and scheduling details by store ID and coordinates, with no DoorDash account required.

Instructions

Get DoorDash store fulfillment details. Returns store fulfillment methods, delivery fee info, and scheduling details from the Android mobile guest experience. No DoorDash account or caller-supplied token is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesDelivery latitude
store_idYesNumeric DoorDash store ID
longitudeYesDelivery longitude

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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. It discloses that no DoorDash account or caller-supplied token is required, and that data comes from the Android mobile guest experience. This adds value beyond a simple 'get details' statement, though it doesn't cover rate limits or error behavior.

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 two sentences with no filler. The first sentence states the core action and return types, and the second adds context about the source and auth requirements—every clause earns its place.

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 three-parameter, no-output-schema tool, the description provides sufficient context: what data is returned, where it comes from, and auth requirements. It is not exhaustive (no mention of error cases or relationship to other doordash tools), but it is adequate for a read-only lookup.

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?

The input schema has 100% coverage with descriptions for all three parameters (store_id, latitude, longitude). The description doesn't add additional meaning beyond the schema, so it meets the baseline but doesn't exceed it.

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 store fulfillment details and specifies the output: fulfillment methods, delivery fee info, and scheduling details. It also identifies the source as the Android mobile guest experience, which distinguishes it from siblings like doordash_store_info, store_menu, and store_reviews.

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 makes the tool's purpose explicit by enumerating the returned data, so an agent can infer when to use it. However, it does not explicitly name alternative tools or state when not to use this one, which would be helpful given the large number of DoorDash sibling tools.

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