Skip to main content
Glama

doordash_orders

Retrieve recent DoorDash order history to track purchases and review past deliveries. Specify a limit to control how many orders are returned.

Instructions

Get recent DoorDash order history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of orders (default 5)

Implementation Reference

  • Registration of the doordash_orders tool.
    server.registerTool(
      "doordash_orders",
      {
        description: "Get recent DoorDash order history",
        inputSchema: {
          limit: z
            .number()
            .optional()
            .default(5)
            .describe("Number of orders (default 5)"),
        },
      },
  • Handler logic for doordash_orders, which retrieves orders using api.orders.getRecentOrders.
      ({ limit }) =>
        wrap(async () => {
          const orders = await api.orders.getRecentOrders(limit);
          if (orders.length === 0) return ok("No recent orders found.");
    
          const lines = ["# Recent Orders\n"];
          for (const order of orders) {
            lines.push(`**${order.storeName}** — ${order.total}`);
            if (order.date) lines.push(`  Date: ${order.date}`);
            if (order.status) lines.push(`  Status: ${order.status}`);
            if (order.items) lines.push(`  Items: ${order.items}`);
            lines.push("");
          }
          return ok(lines.join("\n"));
        }),
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but fails to define 'recent' (time window), mention authentication requirements, or describe error behavior when no orders exist. It implies a read-only operation but lacks explicit behavioral details.

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?

Extremely concise at only five words. Every word earns its place: 'Get' (action), 'recent' (scope), 'DoorDash' (domain), 'order history' (resource). No redundancy or filler.

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?

For a single-parameter read operation, the description is minimally viable. However, given the lack of annotations and output schema, it should ideally specify the time window for 'recent' orders and clarify the return structure.

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 coverage is 100%, so the baseline is 3. The description does not mention the 'limit' parameter, but the schema fully documents it including the default value of 5. The description adds no supplementary semantics about parameter usage.

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?

The description uses a specific verb ('Get') and resource ('DoorDash order history'), and adds the scope 'recent' which clarifies this retrieves historical data rather than active orders. However, it does not explicitly distinguish from sibling tool 'doordash_order_status' which likely checks specific order states.

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

Usage Guidelines2/5

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

No guidance provided on when to use this versus 'doordash_order_status' or prerequisites like authentication (despite 'doordash_login' existing in siblings). No mention of when not to use or alternatives for fetching older orders.

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