warp-agent-mcp

Book Shipment

book

Destructive

Book a quoted shipment using any quote_id or option id returned from a quote tool (Warp or market carrier). Requires quote_id and the full delivery address with the delivery contact's name, phone and email, every time. Pickup can be omitted only when a default shipper is saved on the account. Collect any missing delivery details from the user BEFORE calling. Auth required.

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": {
      "quote_id": "<quote_id>",
      "delivery": "<delivery>"
    },
    "name": "book"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Special instructions for the shipment
`pickup`	No	Pickup address. Required if no default shipper is saved on your account.
`delivery`	Yes	Delivery address and delivery contact. Required on every booking, with every field: street, city, state, ZIP, contact name, phone and email. Warp never fills delivery from past shipments. Ask the user for anything missing before calling book.
`quote_id`	Yes	Quote ID from warp_quote_id (Warp) or id field of any market option returned by a quote tool. Use the id from your MOST RECENT quote — market-option ids rotate on every quote call and stale ids are rejected.
`reference`	No	Your internal reference number
`accessorials`	No	Pickup/delivery accessorial services. Should match the accessorials used when quoting.
`pickup_window`	No	Pickup time window, 24h HH:MM, e.g. { from: '08:00', to: '17:00' }. Defaults to a full business day if omitted.
`delivery_window`	No	Delivery time window, 24h HH:MM, e.g. { from: '09:00', to: '12:00' }. Defaults to a full business day if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / delivery / description

Previous value: -"Delivery address. Required if this lane has not been shipped before."New value: +"Delivery address and delivery contact. Required on every booking, with every field: street, city, state, ZIP, contact name, phone and email. Warp never fills delivery from past shipments. Ask the user for anything missing before calling book."

changedInput schema / properties / delivery / properties / email / description

Previous value: -"Email address (optional — consignee email is often unknown)"New value: +"Delivery contact email. Required by Warp on every booking: ask the user for it if you don't have it."

changedInput schema / properties / delivery / required

Previous value: -[
-  "zipCode",
-  "city",
-  "state",
-  "street",
-  "contactName",
-  "phone"
-]New value: +[
+  "zipCode",
+  "city",
+  "state",
+  "street",
+  "contactName",
+  "phone",
+  "email"
+]

changedInput schema / required

Previous value: -[
-  "quote_id"
-]New value: +[
+  "quote_id",
+  "delivery"
+]

Changed2 schema fields changedSep 11, 2026
- addedInput schema / properties / delivery / properties / zipCode / pattern
```
Added value: +"^\\d{5}$"
```
- addedInput schema / properties / pickup / properties / zipCode / pattern
```
Added value: +"^\\d{5}$"
```
First observedJul 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing auth requirements, the stale-market-id rejection behavior, and the rule that Warp never backfills delivery from past shipments. It does not say what the call produces (booking confirmation, cost charge, or cancel path), which is the main remaining gap for a destructive mutation with no output schema.

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?

Five tight sentences, front-loaded with the verb and the hard prerequisite, followed by the conditional pickup rule and the pre-call checklist. No boilerplate or repetition.

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

Completeness4/5

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

For an 8-parameter mutation with nested address objects and no output schema, the description covers prerequisites, required data, and the pickup edge case well. It leaves unstated what a successful booking returns and whether the booking is cancellable, which an agent committing a destructive shipment would want to know.

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 baseline is 3. The description does add real meaning on quote_id provenance and staleness and on the all-fields-required delivery rule, but the other six parameters (notes, reference, accessorials, windows) are left entirely to the schema.

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?

States a specific verb and resource ("Book a quoted shipment") plus the accepted key source (quote_id or option id from a quote tool), which tells an agent exactly what this does. It does not distinguish itself from sibling booking tools such as parcel_book, batch_book, or multistop_book, so the agent must infer the split.

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

Usage Guidelines4/5

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

Gives strong preconditions: quote_id plus full delivery address every time, pickup omittable only when a default shipper is saved, and an explicit instruction to gather missing details from the user BEFORE calling. It stops short of naming alternatives (parcel_book, batch_book) for non-single-shipment cases.

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

All warp-agent-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.