Skip to main content
Glama

warp-agent-mcp

by io.github.warpfreight

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 + pickup and delivery addresses. Auth required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoSpecial instructions for the shipment
pickupNoPickup address. Required if no default shipper is saved on your account.
deliveryNoDelivery address. Required if this lane has not been shipped before.
quote_idYesQuote 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.
referenceNoYour internal reference number
accessorialsNoPickup/delivery accessorial services. Should match the accessorials used when quoting.
pickup_windowNoPickup time window, 24h HH:MM, e.g. { from: '08:00', to: '17:00' }. Defaults to a full business day if omitted.
delivery_windowNoDelivery 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. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true, so the description adds value by stating 'Auth required' and specifying required inputs. It does not contradict annotations and provides sufficient behavioral context for a booking 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 two sentences with no fluff. The first sentence states purpose precisely, and the second covers prerequisites. Every word earns its place.

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?

Given high schema coverage, the description is adequate for a booking tool. It lacks details about return values (no output schema), but the rules allow that. Overall, it provides enough context for an agent to understand the tool's role.

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 description coverage is 100%, so the schema already documents parameters well. The description adds context by reinforcing required fields and adding 'Auth required', which provides marginal value beyond the schema.

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 clearly states the verb 'Book' and resource 'shipment', and specifies the source of quote IDs (Warp or market carrier). It distinguishes from siblings like batch_book by focusing on a single quoted shipment.

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?

The description provides clear prerequisites (quote_id + addresses) and notes auth required, giving good context for when to use the tool. However, it does not explicitly compare to sibling booking tools or mention when not to use it.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose. Overlapping tools like batch_quote, compare_modes, and per-mode quote tools are clearly differentiated by their scope and use cases. Batch vs single booking are also distinct.

Naming Consistency4/5

Most tools follow a verb_noun pattern in snake_case (e.g., batch_quote, list_bookings). A few like 'analytics' and 'events' are noun-only but still clear. Overall consistent with minor deviations.

Tool Count4/5

26 tools cover a broad logistics domain including quoting, booking, tracking, documents, and account management. While slightly heavy, each tool serves a specific function and the count is reasonable for the scope.

Completeness5/5

The tool set appears complete for freight operations: all major modes quoted, single/batch/multi-stop booking, tracking, documents, invoices, history, and account management. No obvious missing CRUD operations.

Resources