Skip to main content
Glama

doordash_delete_cart

Remove a DoorDash shopping cart by providing its cart ID to clear unwanted items or cancel pending orders.

Instructions

Delete a cart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cart_idYesCart ID to delete

Implementation Reference

  • The handler for the doordash_delete_cart tool, which calls api.cart.deleteCart to remove a cart.
    wrap(async () => {
      await api.cart.deleteCart(cart_id);
      return ok(`Cart ${cart_id} deleted.`);
    }),
  • Registration of the doordash_delete_cart tool with its schema and handler.
    server.registerTool(
      "doordash_delete_cart",
      {
        description: "Delete a cart.",
        inputSchema: { cart_id: z.string().describe("Cart ID to delete") },
      },
      ({ cart_id }) =>
        wrap(async () => {
          await api.cart.deleteCart(cart_id);
          return ok(`Cart ${cart_id} deleted.`);
        }),
    );
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 but offers minimal detail. It states the action is 'Delete' but omits critical context such as whether the deletion is permanent, irreversible, or has cascading effects on active orders.

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 appropriately brief at three words, but it is front-loaded with minimal value. While not verbose, it represents under-specification rather than efficient conciseness given the destructive nature of the operation.

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 operation on a single resource with no output schema, the description is inadequate. It lacks warnings about irreversibility, side effects on associated data (e.g., saved items), or success/failure indicators that would help the agent handle the response.

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% (cart_id is fully documented), establishing baseline 3. The description adds no additional semantic context about the parameter (e.g., format expectations, where to obtain the ID), but none is required given the schema completeness.

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

Purpose2/5

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

The description 'Delete a cart' is tautological, merely restating the tool name without adding specificity. It fails to distinguish this tool from sibling cart operations like doordash_modify_cart (which removes items) or clarify the scope of deletion.

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 guidance provided on when to use this versus alternatives (e.g., using modify_cart to remove specific items instead of deleting the entire cart), nor any prerequisites such as cart state requirements.

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