Skip to main content
Glama

doordash_login

Authenticate with DoorDash using stored credentials to enable restaurant searches, menu browsing, cart management, and order placement through the doordash-mcp server.

Instructions

Log into DoorDash. Reads credentials from ~/.doordash-mcp/config.json. Returns success or requests MFA code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the doordash_login tool. It calls the login function from the injected login API and handles success or MFA requirements.
    server.registerTool(
      "doordash_login",
      {
        description:
          "Log into DoorDash. Reads credentials from ~/.doordash-mcp/config.json. Returns success or requests MFA code.",
      },
      () =>
        wrap(async () => {
          const result = await api.login.login();
          if (result.status === "mfa_required") {
            await api.login.requestMfaCode("email");
            return ok(
              "Verification code sent to your email. Call doordash_verify with the code.",
            );
          }
          return result.status === "success"
            ? ok(result.message)
            : err(result.message);
        }),
    );
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden. It effectively reveals critical behavioral traits: credentials are read from ~/.doordash-mcp/config.json (external dependency) and the tool exhibits dual-mode behavior returning either success or an MFA challenge. It misses session persistence details but covers the essential auth flow.

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?

Three short sentences with zero waste: action declaration, credential source disclosure, and return value specification. Information is front-loaded with the core purpose, and each subsequent sentence adds essential behavioral context not available in structured fields.

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?

For a zero-parameter authentication tool without output schema, the description adequately covers the essential contract: credential source, success path, and MFA challenge path. It could improve by mentioning session prerequisites for sibling tools, but the return behavior disclosure provides sufficient context for invocation.

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?

With zero parameters, the baseline score applies per rubric guidelines. The empty input schema requires no additional semantic clarification, and the description correctly implies no user input is needed at call time (credentials come from config file).

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?

The description opens with the specific action 'Log into DoorDash', clearly identifying both the verb (log into) and resource (DoorDash). It effectively distinguishes itself from sibling operational tools like doordash_search or doordash_checkout by being the sole authentication entry point.

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

Usage Guidelines3/5

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

While the tool's position as the only 'login' tool among operational siblings implies it should be used first, the description lacks explicit guidance on when to invoke it (e.g., 'call before other tools') or when not to (e.g., 'skip if already authenticated'). Usage is implied by context but not stated.

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