Skip to main content
Glama

doordash_add_card

Add a payment card to DoorDash for completing food delivery orders. Provide card number, expiration date, and CVC to enable checkout.

Instructions

Add a payment card to DoorDash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_numberYesFull card number
exp_monthYesExpiration month (e.g. '01')
exp_yearYesExpiration year (e.g. '2029')
cvcYesCVC/CVV code

Implementation Reference

  • Handler for the 'doordash_add_card' tool, which adds a payment card to DoorDash using the api.account.addCard method.
    ({ card_number, exp_month, exp_year, cvc }) =>
      wrap(async () => {
        const result = await api.account.addCard({
          cardNumber: card_number,
          expMonth: exp_month,
          expYear: exp_year,
          cvc,
        });
        return ok(
          `Added ${result.brand} ****${result.last4} (${exp_month}/${exp_year}).`,
        );
      }),
  • Registration of the 'doordash_add_card' tool in the server.
    server.registerTool(
      "doordash_add_card",
      {
        description: "Add a payment card to DoorDash.",
        inputSchema: {
          card_number: z.string().describe("Full card number"),
          exp_month: z.string().describe("Expiration month (e.g. '01')"),
          exp_year: z.string().describe("Expiration year (e.g. '2029')"),
          cvc: z.string().describe("CVC/CVV code"),
        },
      },
      ({ card_number, exp_month, exp_year, cvc }) =>
        wrap(async () => {
          const result = await api.account.addCard({
            cardNumber: card_number,
            expMonth: exp_month,
            expYear: exp_year,
            cvc,
          });
          return ok(
            `Added ${result.brand} ****${result.last4} (${exp_month}/${exp_year}).`,
          );
        }),
    );
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure burden. While 'Add' implies mutation, the description omits security implications of handling sensitive card data, validation behavior, idempotency concerns, or error scenarios (e.g., invalid card numbers).

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 consists of a single six-word sentence that is front-loaded and contains no redundancy. However, it may be excessively brief given the sensitive nature of the operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite complete parameter schema coverage, the tool handles sensitive financial data with no output schema or annotations. The description fails to compensate by explaining success indicators, error handling, security considerations, or prerequisites, leaving significant gaps for an agent attempting to invoke this safely.

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?

The input schema has 100% description coverage for all four parameters (card_number, exp_month, exp_year, cvc). Since the schema fully documents the parameters, the description baseline is appropriate without additional parameter details.

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 states the specific action ('Add') and resource ('payment card') with the target system ('DoorDash'). However, it does not differentiate from sibling tool 'doordash_payment_methods', which likely retrieves cards rather than adding them.

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 provides no guidance on when to use this tool versus alternatives, prerequisites such as requiring an active login session, or whether this should be called before 'doordash_checkout'.

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