Skip to main content
Glama

accept_delivery_quote

Confirm a DoorDash delivery quote and optionally add a tip for the driver to proceed with the order.

Instructions

Accept a delivery quote and optionally add a tip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
external_delivery_idYesThe delivery ID to accept
tipNoThe tip amount in cents (e.g. $5.99 = 599)
dropoff_phone_numberNoPhone number for Dasher to call for dropoff issues (E.164 format)

Implementation Reference

  • The handler function for accept_delivery_quote tool. It destructures the args to separate external_delivery_id and passes the rest to the DoorDash client's deliveryQuoteAccept method.
    handler: (client, args) => {
      const { external_delivery_id, ...acceptArgs } = args;
      return client.deliveryQuoteAccept(external_delivery_id, acceptArgs);
    },
  • Input schema defining the parameters for the accept_delivery_quote tool.
    inputSchema: {
      type: 'object',
      properties: {
        external_delivery_id: { type: 'string', description: 'The delivery ID to accept' },
        tip: { type: 'number', description: 'The tip amount in cents (e.g. $5.99 = 599)' },
        dropoff_phone_number: { type: 'string', description: 'Phone number for Dasher to call for dropoff issues (E.164 format)' },
      },
      required: ['external_delivery_id'],
    },
  • index.js:113-129 (registration)
    The complete tool registration object in the TOOLS array, which includes name, description, schema, and handler. This array is used for both listing tools and dispatching calls.
    {
      name: 'accept_delivery_quote',
      description: 'Accept a delivery quote and optionally add a tip',
      inputSchema: {
        type: 'object',
        properties: {
          external_delivery_id: { type: 'string', description: 'The delivery ID to accept' },
          tip: { type: 'number', description: 'The tip amount in cents (e.g. $5.99 = 599)' },
          dropoff_phone_number: { type: 'string', description: 'Phone number for Dasher to call for dropoff issues (E.164 format)' },
        },
        required: ['external_delivery_id'],
      },
      handler: (client, args) => {
        const { external_delivery_id, ...acceptArgs } = args;
        return client.deliveryQuoteAccept(external_delivery_id, acceptArgs);
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('accept') which implies a mutation, but doesn't describe side effects (e.g., what happens after acceptance), permission requirements, error conditions, or response format. This leaves significant gaps for a mutation tool.

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?

The description is a single, efficient sentence that states the core action and the optional feature. Every word earns its place with zero waste or redundancy.

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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after acceptance, what the response contains, error scenarios, or how this differs from sibling tools. The context signals indicate complexity that isn't addressed.

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 the schema already documents all three parameters thoroughly. The description adds minimal value by mentioning the optional tip, but doesn't provide additional context beyond what's in the schema descriptions. This meets the baseline for high schema coverage.

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 action ('accept') and resource ('delivery quote'), and mentions the optional tip functionality. However, it doesn't explicitly differentiate this from sibling tools like 'create_delivery_quote' or 'update_delivery', which would be needed for a perfect score.

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 'cancel_delivery' or 'update_delivery'. It mentions optional tipping but doesn't explain prerequisites (e.g., must have a pending quote) or timing considerations.

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/amannm/doordash-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server