Skip to main content
Glama

doordash_payment_methods

Retrieve saved payment methods for DoorDash orders to manage billing information and complete transactions.

Instructions

List saved payment methods

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool 'doordash_payment_methods' is registered and implemented directly in src/tools/index.ts as a handler that calls api.account.getPaymentMethods().
    server.registerTool(
      "doordash_payment_methods",
      { description: "List saved payment methods" },
      () =>
        wrap(async () => {
          const methods = await api.account.getPaymentMethods();
          if (methods.length === 0) return err("No payment methods found.");
    
          const lines = ["# Payment Methods\n"];
          for (const m of methods) {
            const def = m.isDefault ? " **(default)**" : "";
            lines.push(
              `- ${m.brand} ****${m.last4} exp ${m.expMonth}/${m.expYear}${def} (ID: ${m.id})`,
            );
          }
          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 the full burden of behavioral disclosure. The verb 'List' implies a read-only operation, but the description fails to disclose what data structure is returned, whether payment details are masked, or if authentication is required to access sensitive payment data.

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 description is exactly three words with zero redundancy. Every word earns its place: 'List' specifies the operation, 'saved' distinguishes from temporary methods, and 'payment methods' identifies the resource.

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 zero-parameter list operation, the description meets minimum viability but has clear gaps. Given the sensitivity of payment data, the description should mention return format (e.g., masked card numbers) or authentication requirements. Without an output schema, the description should compensate by describing what gets returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema contains zero parameters. According to the scoring rubric, zero parameters establishes a baseline score of 4, as there are no parameter semantics to clarify beyond what the empty schema already indicates.

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 clearly states the verb (List) and resource (saved payment methods). While it doesn't explicitly name sibling tools like 'doordash_add_card', the verb choice effectively distinguishes this as a read operation versus the add/modify siblings.

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 tool versus alternatives like 'doordash_add_card' or 'doordash_checkout'. No mention of prerequisites such as requiring authentication before listing payment methods.

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