Skip to main content
Glama
amannm

DoorDash MCP Server

by amannm
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

cancel_delivery

Cancel an active DoorDash delivery order by providing the delivery ID to stop the delivery process.

Instructions

Cancel an existing delivery

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
external_delivery_idYesThe delivery ID to cancel

Implementation Reference

  • index.js:101-112 (registration)
    Registration of the 'cancel_delivery' MCP tool in the TOOLS array, including name, description, input schema requiring external_delivery_id, and handler that calls DoorDashClient.cancelDelivery
    {
  name: 'cancel_delivery',
  description: 'Cancel an existing delivery',
  inputSchema: {
    type: 'object',
    properties: {
      external_delivery_id: { type: 'string', description: 'The delivery ID to cancel' },
    },
    required: ['external_delivery_id'],
  },
  handler: (client, args) => client.cancelDelivery(args.external_delivery_id),
},
  • index.js:111-111 (handler)
    Handler function for the cancel_delivery tool, which invokes the DoorDash SDK's cancelDelivery method with the provided external_delivery_id.
    handler: (client, args) => client.cancelDelivery(args.external_delivery_id),
  • index.js:104-110 (schema)
    Input schema for cancel_delivery tool, defining the required external_delivery_id parameter.
    inputSchema: {
  type: 'object',
  properties: {
    external_delivery_id: { type: 'string', description: 'The delivery ID to cancel' },
  },
  required: ['external_delivery_id'],
},

Tool Definition Quality

C2.9/5.0
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. 'Cancel' implies a destructive mutation, but the description doesn't specify whether this action is reversible, what permissions are required, or what side effects occur (e.g., refunds, notifications). It lacks critical behavioral context 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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse. No unnecessary words or structural issues are present.

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 destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens upon cancellation (e.g., status changes, notifications) or what the tool returns. Given the complexity and lack of structured data, more context is needed for effective agent use.

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%, with the single parameter 'external_delivery_id' documented as 'The delivery ID to cancel'. The description adds no additional meaning beyond this, such as format examples or where to find the ID. Baseline 3 is appropriate since the schema adequately covers the parameter.

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 ('cancel') and target resource ('an existing delivery'), making the purpose immediately understandable. It doesn't differentiate from siblings like 'update_delivery' or 'get_delivery', but the verb 'cancel' is specific enough to convey a distinct operation. No tautology or misleading elements are present.

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 'update_delivery' or what prerequisites might be needed (e.g., delivery must be in a cancellable state). It implies usage for existing deliveries but lacks explicit context or exclusions, leaving the agent to infer when this is appropriate.

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