Skip to main content
Glama

doordash_add_address

Add a delivery address to your DoorDash account by providing street, city, state, ZIP code, and coordinates for accurate order placement.

Instructions

Add a delivery address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
streetYesStreet address
cityYesCity
stateYesState abbreviation
zip_codeYesZIP code
latYesLatitude
lngYesLongitude
google_place_idNoGoogle Place ID

Implementation Reference

  • The handler logic for the 'doordash_add_address' tool. It checks for duplicates before calling the API to add the address.
    ({ street, city, state, zip_code, lat, lng, google_place_id }) =>
      wrap(async () => {
        // Check for duplicate
        const existing = await api.account.getAddresses();
        const dupe = existing.find(
          (a) => a.street === street && a.city === city && a.state === state,
        );
        if (dupe)
          return ok(
            `Address "${street}, ${city}" already exists (ID: ${dupe.id}).`,
          );
    
        await api.account.addAddress({
          street,
          city,
          state,
          zipCode: zip_code,
          lat,
          lng,
          googlePlaceId: google_place_id,
        });
        return ok(`Added address: ${street}, ${city}, ${state} ${zip_code}`);
  • Tool registration for 'doordash_add_address' in src/tools/index.ts.
    server.registerTool(
      "doordash_add_address",
      {
        description: "Add a delivery address.",
        inputSchema: {
          street: z.string().describe("Street address"),
          city: z.string().describe("City"),
          state: z.string().describe("State abbreviation"),
          zip_code: z.string().describe("ZIP code"),
          lat: z.number().describe("Latitude"),
          lng: z.number().describe("Longitude"),
          google_place_id: z.string().optional().describe("Google Place ID"),
        },
      },
Behavior2/5

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

No annotations provided, so description carries full burden of disclosure. Fails to indicate whether the operation is persistent (saves to user profile), idempotent, validates the address against DoorDash's service area, or returns the created address ID.

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?

Single sentence with zero redundancy and clear front-loading. However, extreme brevity contributes to under-specification for a 7-parameter mutation tool.

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?

Inadequate for a complex mutation operation with 7 parameters and no annotations. Lacks explanation of output behavior, error conditions (e.g., invalid address), and relationship to sibling address management tools.

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?

Schema description coverage is 100%, so baseline applies. Description adds no parameter semantics beyond the schema (e.g., doesn't explain that lat/lng are required for geocoding or that google_place_id is optional for validation).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the basic action ('Add') and resource ('delivery address'), but fails to distinguish from sibling 'doordash_set_address'. Does not clarify whether this creates a persistent saved address or adds to a temporary session, leaving scope ambiguous.

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?

Provides no guidance on when to use this tool versus 'doordash_set_address' or 'doordash_addresses'. Missing prerequisites such as authentication requirements or when address validation occurs.

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