warp-agent-mcp

Official

Overview Schema Source Related Servers Discussions(1)Admin

warp_van_quote

Read-only

Quote a firm price for cargo van shipments (1-3 pallets) between US ZIP codes. Enter pallet details, pickup date, and optional services to receive a quote valid for 15 minutes.

Instructions

Quote a cargo van shipment (1-3 pallets, firm price, 15-min expiry)

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": {
      "origin_zip": "<origin_zip>",
      "destination_zip": "<destination_zip>",
      "pallets": "<pallets>",
      "weight_lbs_per_pallet": "<weight_lbs_per_pallet>",
      "pickup_date": "<pickup_date>"
    },
    "name": "warp_van_quote"
  }
}

Input Schema

Name	Required	Description
`origin_zip`	Yes	5-digit US ZIP code
`destination_zip`	Yes	5-digit US ZIP code
`pallets`	Yes	Number of pallets (1-3)
`weight_lbs_per_pallet`	Yes	Weight per pallet in lbs
`pickup_date`	Yes	Pickup date YYYY-MM-DD
`commodity`	No	Commodity description
`pickup_services`	No	Pickup accessorials: pickup-appointment, liftgate-pickup, residential-pickup, limited-access-pickup, inside-pickup, driver-assist-pickup
`delivery_services`	No	Delivery accessorials: delivery-appointment, liftgate-delivery, residential-delivery, limited-access-delivery, inside-delivery, driver-assist-delivery

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.1May 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description adds behavioral context beyond the readOnlyHint annotation: 'firm price, 15-min expiry' indicates the quote's binding nature and limited validity. This informs the agent that the quote is not just a snapshot but a guaranteed offer that expires. No contradiction with 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?

The description is a single sentence that conveys the core purpose and key constraints efficiently. Every word is meaningful, with no redundancy or fluff.

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

Completeness3/5

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

With 8 parameters (5 required) and no output schema, the description would benefit from clarifying what the tool returns (e.g., price, reference number, expiry timestamp). While the description hints at output ('firm price, 15-min expiry'), it lacks explicit details about the response structure, which is needed for a quoting tool.

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?

All 8 parameters have descriptions in the input schema (100% coverage), so the description adds minimal new information about parameters. The description's mention of '1-3 pallets' aligns with the pallets parameter range, but does not elaborate beyond schema details. Baseline 3 is appropriate.

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 explicitly states the tool's purpose: 'Quote a cargo van shipment (1-3 pallets, firm price, 15-min expiry)'. This clearly identifies the resource (cargo van shipment), the action (quote), and key constraints (pallet range, price type, expiry). It distinguishes from sibling tools like warp_box_truck_quote or warp_ltl_quote by specifying cargo van and pallet limits.

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 implies usage for cargo van shipments with 1-3 pallets, providing clear context for when to use this tool. However, it does not explicitly state when not to use it or mention alternative tools for different shipment sizes. The sibling tools (box truck, FTL, LTL) are related but not referenced.

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