Crawlora MCP

doordash_feed

Read-only

Location-aware DoorDash nearby-store discovery feed: store ID, name, cover image and tags, plus rating, price range, delivery fee and ETA when the upstream feed surface reports them. Those metric fields are omitted rather than estimated when it does not, so treat their absence as not-reported. Requires latitude and longitude.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "doordash_feed"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max stores to return.
`offset`	No	Feed offset.
`latitude`	Yes	Consumer latitude.
`longitude`	Yes	Consumer longitude.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely useful behavioral context beyond them — that rating, price range, delivery fee and ETA are omitted rather than estimated when upstream does not report them, and that absence should be read as 'not-reported'. It does not cover pagination or ordering behavior, but the data-quality caveat is real added value.

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?

Three tight sentences, front-loaded with what the tool is, then the return fields, then the omission caveat and the location requirement. No filler; each sentence carries information.

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 an output schema present and annotations covering safety, the description only needs to add non-structural context, and it does — the upstream-reporting caveat is exactly the kind of thing schema and annotations cannot express. Pagination semantics for limit/offset are the only notable gap.

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 limit, offset, latitude and longitude. The description only restates that latitude/longitude are required and adds nothing about limit/offset semantics or expected coordinate format, so the baseline 3 applies.

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 and resource — a location-aware nearby-store discovery feed — and enumerates the returned fields (store ID, name, cover image, tags, rating, price range, delivery fee, ETA). It is distinguishable from doordash_search and doordash_store, but it never names those siblings explicitly to sharpen the contrast.

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 only implied: 'nearby-store discovery' plus the note that latitude and longitude are required tells the agent this is a location-scoped browse call. There is no explicit when-to-use vs when-not, and no routing to alternatives like doordash_search or doordash_store.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?