Skip to main content
Glama

doordash_set_address

Set your active delivery address for DoorDash orders by providing the address ID from your saved addresses.

Instructions

Set the active delivery address.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
address_idYesAddress ID from doordash_addresses

Implementation Reference

  • Registration and handler logic for the 'doordash_set_address' tool. It calls the 'setDefaultAddress' method on the account API and returns a confirmation message.
    server.registerTool(
      "doordash_set_address",
      {
        description: "Set the active delivery address.",
        inputSchema: {
          address_id: z.string().describe("Address ID from doordash_addresses"),
        },
      },
      ({ address_id }) =>
        wrap(async () => {
          await api.account.setDefaultAddress(address_id);
          const addrs = await api.account.getAddresses();
          const match = addrs.find((a) => String(a.id) === String(address_id));
          const name = match ? `${match.street}, ${match.city}` : address_id;
          return ok(`Delivery address set to: ${name}`);
        }),
    );
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. It implies a state mutation ('Set'), but fails to disclose persistence scope (session vs. account), side effects (impact on active cart/checkout flow), error conditions (invalid address_id), or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (4 words) and front-loaded with the verb. However, given the lack of annotations and the tool's mutating nature, this brevity results in under-specification rather than appropriate conciseness—critical behavioral context is omitted.

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 mutation tool with 100% schema coverage, the description provides the minimal viable context. However, gaps remain regarding the 'active' address lifecycle, relationship to checkout workflows, and error handling. Without annotations or an output schema, the description should have elaborated on behavioral implications.

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% (the address_id parameter is fully described in the schema as 'Address ID from doordash_addresses'). The description provides no additional parameter semantics, syntax details, or examples beyond what the schema already documents, warranting 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 uses a specific verb ('Set') and resource ('active delivery address'), clearly distinguishing from sibling 'doordash_add_address' (which creates addresses) by implying selection of an existing address. However, it could explicitly clarify that this selects from previously saved addresses rather than creating new ones.

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 explicit when-to-use guidance or prerequisites are provided. While the parameter description references 'doordash_addresses' (implying it should be called after fetching addresses), there is no explicit guidance on workflow ordering, authentication requirements, or when to use this versus 'doordash_add_address'.

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