Skip to main content
Glama

doordash_join_group_order

Join a DoorDash group order as a guest to add items to a shared cart using a guest session.

Instructions

Join a group order as a guest on behalf of another user. Creates a guest session that can be used with doordash_add_to_cart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cart_idYesGroup cart ID
store_idYesStore ID for the group order
first_nameYesGuest's first name (shown on order labels)
last_nameYesGuest's last name
external_user_idYesExternal user ID to associate with this guest session (e.g. Slack user ID)

Implementation Reference

  • The `doordash_join_group_order` tool is registered in `src/tools/index.ts`. It takes input parameters for cart/store/user details, calls `api.guests.joinGroupOrder` to create a guest session, and returns a confirmation message explaining how to use the `external_user_id` for adding items to the cart.
    server.registerTool(
      "doordash_join_group_order",
      {
        description:
          "Join a group order as a guest on behalf of another user. Creates a guest session that can be used with doordash_add_to_cart.",
        inputSchema: {
          cart_id: z.string().describe("Group cart ID"),
          store_id: z.string().describe("Store ID for the group order"),
          first_name: z
            .string()
            .describe("Guest's first name (shown on order labels)"),
          last_name: z.string().describe("Guest's last name"),
          external_user_id: z
            .string()
            .describe(
              "External user ID to associate with this guest session (e.g. Slack user ID)",
            ),
        },
      },
      ({ cart_id, store_id, first_name, last_name, external_user_id }) =>
        wrap(async () => {
          const session = await api.guests.joinGroupOrder({
            cartId: cart_id,
            storeId: store_id,
            externalUserId: external_user_id,
            firstName: first_name,
            lastName: last_name,
          });
          return ok(
            `**${session.firstName} ${session.lastName}** joined the group order.\n` +
              `External user ID: ${external_user_id}\n\n` +
              `Use doordash_add_to_cart with \`external_user_id: "${external_user_id}"\` and \`cart_id: "${cart_id}"\` to add items on their behalf.`,
          );
        }),
    );
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the creation of a 'guest session' and its purpose, but omits session lifecycle (expiration), idempotency, error conditions if cart is closed/full, or whether this overwrites existing guest sessions.

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 highly efficient sentences. First establishes purpose and actor, second establishes the output/relationship to next step. No filler words, front-loaded with action, every sentence earns its place.

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?

Adequate for workflow understanding but incomplete given no output schema exists. Mentions session creation but doesn't describe the return structure (session ID format) or failure modes (invalid cart_id, closed orders). Given 5 required params and mutation behavior, needs richer behavioral disclosure.

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% with clear descriptions for all 5 parameters. Description adds minimal semantic value beyond the schema but provides the 'guest' context that explains why first_name/last_name are required. Baseline 3 appropriate when schema is comprehensive.

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?

Excellent clarity with specific verb 'Join', resource 'group order', role 'as a guest', and context 'on behalf of another user'. Clearly distinguishes from sibling 'doordash_create_group_order' (which creates) and 'doordash_add_to_cart' (which consumes the session).

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

Usage Guidelines4/5

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

Explicitly names the workflow continuation: 'can be used with doordash_add_to_cart', establishing the correct sequence. However, lacks explicit 'when not to use' guidance or prerequisites (e.g., requiring an active group order cart_id).

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