Skip to main content
Glama

warp-agent-mcp

by io.github.warpfreight

Batch Book Shipments

batch_book
Destructive

Book MANY already-quoted lanes in ONE call (sequential, one card charge per row). Use this after batch_quote when the user says "book all of them" or "book rows 1, 3, 5" — do NOT call book in a loop. Each row needs a quote_id (the same one batch_quote returned for that row). Pickup/delivery default to the shared addresses at the top level so a single warehouse → many destinations only needs one address pair. Returns a progress card showing per-row Booked/Failed status with tracking numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookingsYesArray of bookings to confirm (1-25). Each is one freight shipment, one card charge.
shared_notesNoNotes applied to every row without their own.
shared_pickupNoPickup address applied to every row that doesn't supply its own (FBA case: one warehouse → many destinations).
shared_deliveryNoDelivery address applied to every row that doesn't supply its own. Uncommon (usually each row goes somewhere different).
shared_referenceNoReference applied to every row without its own.
shared_accessorialsNo
shared_pickup_windowNo
shared_delivery_windowNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations provide destructiveHint=true. Description adds 'sequential, one card charge per row', fallback mechanism for shared parameters, and return of progress card with per-row status—valuable behavioral context beyond annotations.

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?

Front-loaded with purpose and usage, then parameter behavior, then return. Every sentence adds value. No redundancy or 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?

Covers purpose, usage, parameter fallbacks, return value (progress card), and specific use case (FBA). No output schema exists, but description explains output adequately. Complete and self-contained.

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

Parameters5/5

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

Adds meaning beyond schema: explains quote_id must be from this session, pickup/delivery default to shared addresses, shared_pickup is for FBA case. Schema coverage 63% is compensated by rich contextual details.

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 specific verb 'Book' and resource 'MANY already-quoted lanes in ONE call', distinguishing from siblings like 'book' (single) and 'multistop_book'. It clarifies it's for after batch_quote, making purpose unambiguous.

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?

Explicitly instructs when to use (after batch_quote on 'book all of them' etc.) and when not to ('do NOT call book in a loop'), and mentions alternatives (batch_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 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