Skip to main content
Glama

doordash_group_order_status

View group order items broken down by person using the group cart ID to track contributions and status.

Instructions

View a group order's items broken down by person.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cart_idYesGroup cart ID

Implementation Reference

  • The tool 'doordash_group_order_status' is registered and implemented in src/tools/index.ts. It calls the 'getGroupCart' method from the group API to fetch order details and formats them as a markdown string.
      "doordash_group_order_status",
      {
        description: "View a group order's items broken down by person.",
        inputSchema: {
          cart_id: z.string().describe("Group cart ID"),
        },
      },
      ({ cart_id }) =>
        wrap(async () => {
          const gc = await api.group.getGroupCart(cart_id);
          const lines = [
            "# Group Order\n",
            `Share link: ${gc.shareUrl}`,
            `Subtotal: $${(gc.subtotal / 100).toFixed(2)}\n`,
          ];
    
          if (gc.members.length === 0) {
            lines.push("No one has added items yet.");
          }
    
          for (const member of gc.members) {
            const status = member.isFinalized ? "finalized" : "still adding";
            lines.push(`## ${member.name} (${status})`);
            for (const item of member.items) {
              const price = item.price ? `$${(item.price / 100).toFixed(2)}` : "";
              lines.push(
                `- ${item.quantity}x ${item.name} ${price} (item ID: ${item.id})`,
              );
            }
            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, so the description carries full disclosure burden. It indicates a read operation via 'View' and adds valuable context about the output structure ('broken down by person'), but lacks critical behavioral details like error handling for invalid cart_id, authentication requirements, or whether the breakdown includes pricing per person.

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 single sentence is appropriately front-loaded with the action verb, contains zero redundancy, and efficiently communicates the core value proposition without filler words. Length is optimal for the tool's simplicity.

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 low complexity (single string parameter, 100% schema coverage) and lack of output schema, the description adequately explains the return value concept (items by person). It meets minimum viability but could enhance completeness by mentioning the typical flow (use after create/join group order).

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 ('Group cart ID'), the schema fully documents the parameter. The description implies the cart_id refers to a group order but adds no semantic detail beyond what the schema already provides, 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 specific verb 'View' with clear resource 'group order's items' and adds distinguishing detail 'broken down by person' that differentiates it from sibling tools like doordash_order_status (general status) and doordash_cart (simple item list). However, it could explicitly clarify the distinction from regular 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?

No explicit when-to-use guidance or alternatives are mentioned. While 'group order' implies usage for group orders specifically, the description fails to specify when to use this versus doordash_order_status or doordash_cart, or prerequisites like requiring an active group cart.

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