Skip to main content
Glama

doordash_verify

Complete DoorDash login by entering a 6-digit verification code to authenticate and access delivery services.

Instructions

Complete DoorDash login with a verification code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes6-digit verification code

Implementation Reference

  • The tool 'doordash_verify' is registered and implemented in src/tools/index.ts. It calls the 'verifyMfa' method of the 'login' API.
    server.registerTool(
      "doordash_verify",
      {
        description: "Complete DoorDash login with a verification code.",
        inputSchema: {
          code: z.string().describe("6-digit verification code"),
        },
      },
      ({ code }) =>
        wrap(async () => {
          const result = await api.login.verifyMfa(code);
          return result.status === "success"
            ? ok(result.message)
            : err(result.message);
        }),
    );
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions completing login but fails to explain critical behavioral traits: whether this establishes a persistent session, modifies authentication state, or has idempotency concerns. The agent cannot determine side effects from the description alone.

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 single-sentence description is efficiently structured and front-loaded with the action verb. However, given the complete absence of annotations and output schema, the extreme brevity leaves significant gaps in agent guidance that a slightly longer description could address.

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 single-parameter tool with full schema coverage, the description is minimally adequate. However, given no output schema exists and this is part of a multi-step authentication flow (evidenced by sibling doordash_login), the description should ideally clarify the prerequisite step or success/failure outcomes to be complete.

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, the input schema already fully documents the 'code' parameter as a '6-digit verification code'. The description mentions 'verification code' but adds no additional semantic context (e.g., where the code comes from, expiration constraints) beyond the schema, meriting the baseline score.

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 specific action (complete login) and resource (DoorDash) using a distinct mechanism (verification code), which implicitly distinguishes it from the sibling 'doordash_login' tool. However, it doesn't explicitly clarify the two-step workflow relationship.

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?

While the phrase 'Complete DoorDash login' implies this is a secondary step requiring a verification code, there is no explicit guidance on when to use this versus doordash_login, nor does it state the prerequisite of initiating login first or what happens if called without a pending verification.

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