warp-agent-mcp

Book Multi-stop FTL

multistop_book

Destructive

Book a multi-stop FTL route quoted by multistop_quote. Send one shipments[] leg per pickup→delivery pair riding the truck (minimum 2 legs), each leg referencing the quoted stop sequence by stop_index with full address + arrival window. No card charge fires from this call — multi-stop pricing settles via your Warp account. 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>",
      "shipments": "<shipments>"
    },
    "name": "multistop_book"
  }
}

Input Schema

Name	Required	Description	Default
`quote_id`	Yes	Quote ID from multistop_quote (PRICING_MULTI_…). Use the id from your MOST RECENT quote — ids expire and rotate.
`shipments`	Yes	One leg per pickup→delivery pair (the gateway requires at least 2)

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedOct 30, 2026
- removedInput schema / properties / shipments / items / properties / delivery_info / properties / address / $ref
```
Removed value: -"#/properties/shipments/items/properties/pickup_info/properties/address"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / address / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / address / description
```
Added value: +"Full address of this stop"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / address / properties
```
Added value: +{
+  "city": {
+    "description": "City name",
+    "type": "string"
+  },
+  "state": {
+    "description": "2-letter state code",
+    "type": "string"
+  },
+  "street": {
+    "description": "Street address",
+    "type": "string"
+  },
+  "zipcode": {
+    "description": "5-digit ZIP — must match the quoted stop's ZIP",
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / address / required
```
Added value: +[
+  "street",
+  "city",
+  "state",
+  "zipcode"
+]
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / address / type
```
Added value: +"object"
```
- removedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_email / $ref
```
Removed value: -"#/properties/shipments/items/properties/pickup_info/properties/contact_email"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_email / description
```
Added value: +"Contact email"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_email / type
```
Added value: +"string"
```
- removedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_name / $ref
```
Removed value: -"#/properties/shipments/items/properties/pickup_info/properties/contact_name"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_name / description
```
Added value: +"Contact full name"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_name / type
```
Added value: +"string"
```
- removedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_phone / $ref
```
Removed value: -"#/properties/shipments/items/properties/pickup_info/properties/contact_phone"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_phone / description
```
Added value: +"Contact phone"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / contact_phone / type
```
Added value: +"string"
```
- removedInput schema / properties / shipments / items / properties / delivery_info / properties / stop_index / $ref
```
Removed value: -"#/properties/shipments/items/properties/pickup_info/properties/stop_index"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / stop_index / description
```
Added value: +"Index into the quoted stop sequence: 0 = first pickup, then intermediate stops in order, last = final delivery. multistop_quote echoes the sequence as stop_sequence."
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / stop_index / minimum
```
Added value: +0
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / stop_index / type
```
Added value: +"integer"
```
- removedInput schema / properties / shipments / items / properties / delivery_info / properties / window_time / $ref
```
Removed value: -"#/properties/shipments/items/properties/pickup_info/properties/window_time"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / window_time / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / window_time / description
```
Added value: +"Arrival window for this stop"
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / window_time / properties
```
Added value: +{
+  "from": {
+    "description": "Window open, ISO date-time, e.g. 2026-06-22T08:00:00.000Z",
+    "type": "string"
+  },
+  "to": {
+    "description": "Window close, ISO date-time, e.g. 2026-06-22T23:59:59.000Z",
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / window_time / required
```
Added value: +[
+  "from",
+  "to"
+]
```
- addedInput schema / properties / shipments / items / properties / delivery_info / properties / window_time / type
```
Added value: +"object"
```
First observedJul 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare destructiveHint=true but say nothing about consequences; the description adds real context the annotations can't: no card charge fires, pricing settles via the Warp account, and auth is required. It doesn't explain why the call is flagged destructive (commitment/cancellation implications) or what it returns, so it stops short of full coverage.

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?

Four short sentences, each carrying a distinct fact (source quote, leg structure, payment behavior, auth). The critical routing and structural constraints are front-loaded with no filler.

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 a two-parameter mutation with no output schema, the description covers the prerequisites, the leg/stop_index model, and the payment path. The remaining gap is the return value — an agent isn't told what a successful booking yields (confirmation id, load reference) to chain into track or get_documents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds conceptual meaning: shipments[] is one leg per pickup→delivery pair riding the truck, and each leg's stop_index references the quoted stop sequence echoed by multistop_quote. That framing is not derivable from the schema's field-level descriptions alone.

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?

States a specific verb and resource ('Book a multi-stop FTL route') and immediately ties it to the originating sibling ('quoted by multistop_quote'), which separates it from book, batch_book, and ftl_quote without opening any schema. The minimum-2-legs constraint further pins the scope.

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?

It makes the prerequisite explicit (a route from multistop_quote, referencing stop_index) and states the structural condition (one leg per pickup→delivery pair, minimum 2). It does not explicitly name an alternative for single-stop bookings, so the when-not is left implicit.

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.