Skip to main content
Glama

submit_order

Destructive

Places a real DoorDash order and charges the user's payment method after preview and explicit terminal approval; use only after the user confirms the order.

Instructions

Place the order — charges the user's real payment method. HARD GATE: the terminal asks the user to type 'yes'; a decline returns declined_by_user. Call ONLY after: (1) preview shown, (2) tip explicitly confirmed (delivery; pickup = 0 without asking), (3) payment method named to the user, (4) the user clearly said to place it. NOT idempotent — never retry without checking get_order_status first. Report success only when the response's lifecycle.order_created is true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cart_uuid": "<cart_uuid>",
      "tip_cents": "<tip_cents>",
      "confirmation_summary": "<confirmation_summary>",
      "intent": "<intent>"
    },
    "name": "submit_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesOne short line stating who this is for and the goal, e.g. 'Help the user order dinner'. DO NOT include the user's verbatim words, dietary/health/religious details, budgets, names, or other personal specifics — a generic goal is expected.
card_idNoMUST match the preview: pass the same card_id the quote was priced on, so the card charged is the card the user was told about. ASAP orders only. With team_id/budget_id the card covers only what the budget doesn't.
team_idNoWork benefits: quote.team_id from preview
priorityNoMUST match the preview: pass iff the previewed quote used priority
budget_idNoWork benefits: chosen budget id
cart_uuidYesCart UUID
tip_centsYesDasher tip in CENTS (500 = $5.00). 0 only on explicit decline or pickup.
fulfillmentNoOnly to match a mode explicitly set at preview
expense_codeNoRequired when budget expense_code_mode != NONE
expense_notesNoRequired when budget is_expense_note_required
scheduled_timeNoMust match the value used in preview, if any
team_account_idNoWork benefits: budget's team_account_id when present
no_apply_creditsNoMUST match the preview: pass iff the user opted out of credits there
confirmation_summaryYesShort human-readable summary shown at the terminal gate: store, items, total, tip, card (brand+last4), ETA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / card_id
      Added value: +{
      +  "description": "MUST match the preview: pass the same card_id the quote was priced on, so the card charged is the card the user was told about. ASAP orders only. With team_id/budget_id the card covers only what the budget doesn't.",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive/open-world annotations, it discloses real payment charging, the terminal 'yes' confirmation gate, declined_by_user behavior, non-idempotency, and a success criterion tied to lifecycle.order_created. These are exactly the behavioral traits an agent needs for a destructive, irreversible operation.

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 front-loaded with the most important fact — real payment charge — followed by the hard gate and retry warning. Every sentence carries operational weight, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the definition covers the required preconditions, non-idempotency, decline handling, and the exact success signal to check. An agent has enough information to decide whether to call it and how to interpret the result.

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 coverage is 100%, so the detailed field descriptions already carry most parameter semantics. The tool description adds useful preconditions such as tip confirmation and pickup=0 handling, but it does not materially document the 14 parameters beyond what the schema provides, fitting the baseline for full schema coverage.

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

Purpose5/5

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

The description states a specific verb and resource — placing a real-charge order — and immediately distinguishes it from preview/status siblings by naming preview and get_order_status. It makes the financial consequence explicit, so an agent cannot confuse it with a harmless preview action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit hard gate with four conditions that must precede the call: preview shown, tip confirmed, payment method named, and clear user intent. It also says not to retry without checking get_order_status and names the exact decline outcome, which is unusually actionable routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.