Skip to main content
Glama

create_delivery

Create a new DoorDash delivery request by specifying pickup and dropoff details, contact information, and order value to arrange item transportation.

Instructions

Create a new delivery request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
external_delivery_idYesUnique identifier for the delivery
pickup_addressYesPickup address
pickup_business_nameNoBusiness name for pickup
pickup_phone_numberNoPhone number for pickup
pickup_instructionsNoSpecial instructions for pickup
dropoff_addressYesDropoff address
dropoff_business_nameNoBusiness name for dropoff
dropoff_phone_numberNoPhone number for dropoff
dropoff_instructionsNoSpecial instructions for dropoff
order_valueNoValue of the order in cents

Implementation Reference

  • index.js:87-87 (handler)
    Handler function that executes the create_delivery tool by calling client.createDelivery(args) on the DoorDashClient.
    handler: (client, args) => client.createDelivery(args),
  • Input schema defining the required and optional parameters for the create_delivery tool.
    inputSchema: {
      type: 'object',
      properties: {
        external_delivery_id: { type: 'string', description: 'Unique identifier for the delivery' },
        pickup_address: { type: 'string', description: 'Pickup address' },
        pickup_business_name: { type: 'string', description: 'Business name for pickup' },
        pickup_phone_number: { type: 'string', description: 'Phone number for pickup' },
        pickup_instructions: { type: 'string', description: 'Special instructions for pickup' },
        dropoff_address: { type: 'string', description: 'Dropoff address' },
        dropoff_business_name: { type: 'string', description: 'Business name for dropoff' },
        dropoff_phone_number: { type: 'string', description: 'Phone number for dropoff' },
        dropoff_instructions: { type: 'string', description: 'Special instructions for dropoff' },
        order_value: { type: 'number', description: 'Value of the order in cents' },
      },
      required: ['external_delivery_id', 'pickup_address', 'dropoff_address'],
    },
  • index.js:68-88 (registration)
    Registration of the 'create_delivery' tool within the TOOLS array, used by the MCP server for tool listing and execution.
    {
      name: 'create_delivery',
      description: 'Create a new delivery request',
      inputSchema: {
        type: 'object',
        properties: {
          external_delivery_id: { type: 'string', description: 'Unique identifier for the delivery' },
          pickup_address: { type: 'string', description: 'Pickup address' },
          pickup_business_name: { type: 'string', description: 'Business name for pickup' },
          pickup_phone_number: { type: 'string', description: 'Phone number for pickup' },
          pickup_instructions: { type: 'string', description: 'Special instructions for pickup' },
          dropoff_address: { type: 'string', description: 'Dropoff address' },
          dropoff_business_name: { type: 'string', description: 'Business name for dropoff' },
          dropoff_phone_number: { type: 'string', description: 'Phone number for dropoff' },
          dropoff_instructions: { type: 'string', description: 'Special instructions for dropoff' },
          order_value: { type: 'number', description: 'Value of the order in cents' },
        },
        required: ['external_delivery_id', 'pickup_address', 'dropoff_address'],
      },
      handler: (client, args) => client.createDelivery(args),
    },
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. 'Create a new delivery request' implies a write/mutation operation but provides no information about permissions required, whether this is idempotent, what happens on failure, rate limits, or what the response contains. For a creation tool with 10 parameters and no annotation coverage, this is a significant gap in behavioral transparency.

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 gets straight to the point with zero wasted words. It's appropriately sized for a tool with a clear primary function and doesn't bury important information in unnecessary verbiage.

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 creation tool with 10 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens after creation, what the expected response looks like, error conditions, or how this tool relates to the sibling tools. The agent would be left guessing about important behavioral aspects despite the comprehensive parameter schema.

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?

The schema description coverage is 100%, with all 10 parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 verb ('Create') and resource ('delivery request'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'create_delivery_quote', which appears to be a related creation operation. The description is specific but lacks sibling distinction.

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 'create_delivery_quote' or 'accept_delivery_quote'. There's no mention of prerequisites, sequencing, or contextual factors that would help an agent choose between these similar delivery-related creation tools.

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