warp-agent-mcp

Book Parcel (FedEx)

parcel_book

Destructive

Book a FedEx parcel option from parcel_quote. Requires the quote_id the user chose and the full delivery address with contact name and phone; pickup can be omitted only when a default shipper is saved. ZIPs must match the quote. The packages are the ones quoted (not resent). Charges the account like book does (terms accounts are billed on terms; others pay from the Warp balance, with the saved card covering any shortfall). Only call after the user explicitly confirms this option and price. 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": "parcel_book"
  }
}

Input Schema

Name	Required	Description
`pickup`	No	Pickup address. Required if no default shipper is saved.
`delivery`	Yes	Delivery address and contact, every required field
`quote_id`	Yes	quote_id of the option the user chose, from your MOST RECENT parcel_quote
`reference`	No	Your reference (PO, order number)
`pickup_window`	No	Local pickup window, 24h HH:MM. Defaults to 08:00-20:00.
`delivery_window`	No	Local delivery window, 24h HH:MM. Defaults to 08:00-20:00.

Schema Changelog

Changes observed during successful MCP inspections.

Changed34 schema fields changedOct 30, 2026
- removedInput schema / properties / delivery / properties / city / $ref
```
Removed value: -"#/properties/pickup/properties/city"
```
- addedInput schema / properties / delivery / properties / city / description
```
Added value: +"City"
```
- addedInput schema / properties / delivery / properties / city / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / company / $ref
```
Removed value: -"#/properties/pickup/properties/company"
```
- addedInput schema / properties / delivery / properties / company / description
```
Added value: +"Company / location name"
```
- addedInput schema / properties / delivery / properties / company / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / contactName / $ref
```
Removed value: -"#/properties/pickup/properties/contactName"
```
- addedInput schema / properties / delivery / properties / contactName / description
```
Added value: +"Contact full name"
```
- addedInput schema / properties / delivery / properties / contactName / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / email / $ref
```
Removed value: -"#/properties/pickup/properties/email"
```
- addedInput schema / properties / delivery / properties / email / description
```
Added value: +"Contact email"
```
- addedInput schema / properties / delivery / properties / email / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / phone / $ref
```
Removed value: -"#/properties/pickup/properties/phone"
```
- addedInput schema / properties / delivery / properties / phone / description
```
Added value: +"Contact phone. FedEx requires it on both stops: ask the user if you don't have it."
```
- addedInput schema / properties / delivery / properties / phone / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / refNum / $ref
```
Removed value: -"#/properties/pickup/properties/refNum"
```
- addedInput schema / properties / delivery / properties / refNum / description
```
Added value: +"Reference for this stop (PO/SO)"
```
- addedInput schema / properties / delivery / properties / refNum / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / specialInstruction / $ref
```
Removed value: -"#/properties/pickup/properties/specialInstruction"
```
- addedInput schema / properties / delivery / properties / specialInstruction / description
```
Added value: +"Instructions for this stop"
```
- addedInput schema / properties / delivery / properties / specialInstruction / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / state / $ref
```
Removed value: -"#/properties/pickup/properties/state"
```
- addedInput schema / properties / delivery / properties / state / description
```
Added value: +"2-letter state code"
```
- addedInput schema / properties / delivery / properties / state / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / street / $ref
```
Removed value: -"#/properties/pickup/properties/street"
```
- addedInput schema / properties / delivery / properties / street / description
```
Added value: +"Street address"
```
- addedInput schema / properties / delivery / properties / street / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / street2 / $ref
```
Removed value: -"#/properties/pickup/properties/street2"
```
- addedInput schema / properties / delivery / properties / street2 / description
```
Added value: +"Suite / unit"
```
- addedInput schema / properties / delivery / properties / street2 / type
```
Added value: +"string"
```
- removedInput schema / properties / delivery / properties / zipCode / $ref
```
Removed value: -"#/properties/pickup/properties/zipCode"
```
- addedInput schema / properties / delivery / properties / zipCode / description
```
Added value: +"5-digit ZIP; must match the quoted ZIP"
```
- addedInput schema / properties / delivery / properties / zipCode / pattern
```
Added value: +"^\\d{5}$"
```
- addedInput schema / properties / delivery / properties / zipCode / type
```
Added value: +"string"
```
AddedOct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the destructive mutation annotations, it discloses billing behavior, default-shipper pickup conditions, package reuse from the quote, auth requirements, and the explicit user-confirmation gate. This is substantial behavioral context an agent needs before invoking a destructive booking 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 dense but well front-loaded: purpose first, then requirements, constraints, billing behavior, and the confirmation gate. Every sentence adds operational value without 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 booking tool with nested address objects and no output schema, the description covers the critical preconditions, billing side effects, confirmation requirement, and auth. It gives enough context for an agent to decide whether and how to call it.

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 meaningful semantics: pickup is conditional on a saved default shipper, delivery requires contact name and phone, ZIPs must match the quote, and packages are the quoted ones rather than newly supplied.

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: booking a FedEx parcel option sourced from parcel_quote. It distinguishes this from a generic booking flow by tying it explicitly to a prior parcel quote and quote_id.

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 explicit when-to-use conditions: only after the user confirms the option and price, using the quote_id from the most recent parcel_quote. It also states when pickup may be omitted and that ZIPs must match the quote.

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.