Skip to main content
Glama

doordash_menu

Retrieve restaurant menu details using a store ID obtained from doordash_search to view available items and prices.

Instructions

Get a restaurant's menu by store ID. Use doordash_search first to find the store ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesDoorDash store ID (numeric)

Implementation Reference

  • The handler for `doordash_menu` is defined and registered in `src/tools/index.ts`. It takes a `store_id`, fetches the menu using `api.menu.getStoreMenu`, and formats it as a string for the model.
    server.registerTool(
      "doordash_menu",
      {
        description:
          "Get a restaurant's menu by store ID. Use doordash_search first to find the store ID.",
        inputSchema: {
          store_id: z.string().describe("DoorDash store ID (numeric)"),
        },
      },
      ({ store_id }) =>
        wrap(async () => {
          const menu = await api.menu.getStoreMenu(store_id);
          const lines: string[] = [];
          lines.push(`# ${menu.name}`);
          if (menu.description) lines.push(`*${menu.description}*`);
          if (menu.isConvenience) lines.push("**Type: Convenience store**");
          lines.push("");
          if (menu.rating) lines.push(`Rating: ${menu.rating}`);
          if (menu.deliveryMinutes)
            lines.push(`Delivery: ~${menu.deliveryMinutes} min`);
          if (menu.priceRange) lines.push(`Price: ${menu.priceRange}`);
          if (menu.address) lines.push(`Address: ${menu.address}`);
          lines.push("");
    
          if (menu.isConvenience) {
            lines.push("This is a convenience store with a large catalog.");
            lines.push(
              "Use `doordash_convenience_search` with this store ID to find specific items.",
            );
            return ok(lines.join("\n"));
          }
    
          for (const cat of menu.categories) {
            lines.push(`## ${cat.name}`);
            for (const item of cat.items) {
              let line = `- **${item.name}** ${item.displayPrice}`;
              if (!item.quickAddEligible) line += " ⚙️";
              if (item.description) {
                const desc =
                  item.description.length > 80
                    ? item.description.slice(0, 80) + "..."
                    : item.description;
                line += ` — ${desc}`;
              }
              line += ` (ID: ${item.id})`;
              lines.push(line);
            }
            lines.push("");
          }
    
          return ok(lines.join("\n"));
        }),
Behavior3/5

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

No annotations are provided, placing full disclosure burden on the description. While 'Get' implies a read-only operation, the description lacks details on return format (menu structure), error handling for invalid store IDs, or rate limiting. It meets minimum behavioral disclosure for a simple getter.

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?

Two sentences with zero redundancy: first establishes purpose, second provides workflow prerequisite. Information is front-loaded and every word serves a specific function for agent decision-making.

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?

Given the tool's low complexity (single required parameter) and lack of output schema, the description adequately covers the essential workflow context. Could be improved by describing the menu data structure returned, but sufficient for agent selection and invocation.

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?

With 100% schema description coverage ('DoorDash store ID (numeric)'), the schema carries the semantic load. The description references 'store ID' aligning with the parameter name but adds no additional format guidance, constraints, or examples beyond the schema definition.

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 specific action (Get), resource (restaurant's menu), and required input mechanism (by store ID). It effectively distinguishes this retrieval tool from sibling ordering and search tools by specifying the exact workflow entry point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes the correct sequencing by naming the prerequisite tool: 'Use doordash_search first to find the store ID.' This provides clear when-to-use guidance and establishes the dependency relationship with doordash_search.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ashah360/doordash-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server