Skip to main content
Glama

doordash_order_status

Check the status of a DoorDash order by providing the order ID to track delivery progress and updates.

Instructions

Check the status of a DoorDash order

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesOrder UUID from doordash_place_order

Implementation Reference

  • The 'doordash_order_status' tool is registered in src/tools/index.ts. The handler calls 'api.checkout.getOrderStatus(order_id)' and formats the output into a markdown string.
    server.registerTool(
      "doordash_order_status",
      {
        description: "Check the status of a DoorDash order",
        inputSchema: {
          order_id: z.string().describe("Order UUID from doordash_place_order"),
        },
      },
      ({ order_id }) =>
        wrap(async () => {
          const status = await api.checkout.getOrderStatus(order_id);
          const lines = ["# Order Status\n", `Order ID: ${order_id}`];
          for (const [key, val] of Object.entries(status)) {
            if (key !== "__typename" && val != null) lines.push(`${key}: ${val}`);
          }
          return ok(lines.join("\n"));
        }),
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not specify what status information is returned (e.g., preparation stage, delivery ETA), whether the operation is idempotent, or if there are rate limits. The verb 'Check' implies read-only but does not confirm safety or side effects.

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?

The description is a single, efficient sentence with no wasted words. However, given the lack of annotations and output schema, it may be overly terse—slightly more detail on return value or distinguishing scope would add value without sacrificing clarity.

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 simple single-parameter tool, the description is minimally viable. However, without an output schema, it should ideally hint at what status details are returned (e.g., 'preparing', 'delivered') to set caller expectations, which it does not.

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 ('Order UUID from doordash_place_order'), the schema fully documents the single parameter. The description adds no additional semantic context about the parameter, meeting the baseline for high-coverage schemas.

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 ('Check') and resource ('status of a DoorDash order'), clearly indicating a read operation on order state. However, it does not explicitly differentiate from sibling tools like 'doordash_orders' (likely a list operation) or 'doordash_group_order_status'.

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?

The description text provides no guidance on when to use this tool versus alternatives (e.g., 'doordash_orders' for listing history). While the input schema notes the order_id comes from 'doordash_place_order', the description itself lacks explicit when/when-not instructions.

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