Skip to main content
Glama

doordash_addresses

Retrieve saved delivery addresses to streamline DoorDash order placement and management.

Instructions

List saved delivery addresses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'doordash_addresses' tool handler is defined and registered in src/tools/index.ts. It calls the 'api.account.getAddresses()' method to fetch and list saved addresses.
    server.registerTool(
      "doordash_addresses",
      { description: "List saved delivery addresses" },
      () =>
        wrap(async () => {
          const addrs = await api.account.getAddresses();
          if (addrs.length === 0) return err("No saved addresses.");
    
          const lines = ["# Delivery Addresses\n"];
          for (const a of addrs) {
            lines.push(
              `- ${a.street}, ${a.city}, ${a.state} ${a.zipCode} (ID: ${a.id})`,
            );
          }
          return ok(lines.join("\n"));
        }),
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List' implies a read-only operation, the description fails to confirm safety traits, disclose return format (array of address objects), mention authentication requirements, or note whether the default address is marked specially.

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 is extremely brief at only four words, containing no wasted text. However, it is so terse that it borders on under-specification rather than optimal conciseness, lacking a period or complete sentence structure that would formally signal the end of the description.

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?

Given the tool's low complexity (zero parameters, no nested objects) and lack of output schema, the description is minimally adequate but incomplete. It fails to hint at the return structure or explain what constitutes a 'saved' address versus other address types in the DoorDash ecosystem.

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 tool has zero parameters and the input schema is an empty object. Per the rubric, 0 parameters establishes a baseline of 4, as there are no parameter semantics to elaborate upon beyond what the schema already conveys.

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 uses a specific verb 'List' and identifies the resource as 'saved delivery addresses', distinguishing it from sibling tools like doordash_add_address (which adds) and doordash_set_address (which likely sets active). However, it lacks explicit scope clarification (e.g., 'for the authenticated user') that would make it a 5.

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 like doordash_set_address or doordash_add_address. It does not mention prerequisites (e.g., requiring authentication) or typical use cases (e.g., 'use before placing an order to view available addresses').

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