Skip to main content
Glama

warp-agent-mcp

by io.github.warpfreight
OverviewDiscussionsAdmin

Get Cargo Van Quote

van_quote
Read-only

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
palletsYesNumber of pallets (1-3)
width_inNoPer-pallet width in inches (defaults to 40)
commodityNoCommodity description
height_inNoPer-pallet height in inches (defaults to 48)
length_inNoPer-pallet length in inches (defaults to 48)
origin_zipYes5-digit US ZIP code
pickup_dateYesPickup date YYYY-MM-DD
destination_zipYes5-digit US ZIP code
pickup_servicesNoPickup accessorials: pickup-appointment, liftgate-pickup, residential-pickup, limited-access-pickup, inside-pickup, driver-assist-pickup
delivery_servicesNoDelivery accessorials: delivery-appointment, liftgate-delivery, residential-delivery, limited-access-delivery, inside-delivery, driver-assist-delivery
weight_lbs_per_palletYesWeight per pallet in lbs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / height_in
      Added value: +{
+  "description": "Per-pallet height in inches (defaults to 48)",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / length_in
      Added value: +{
+  "description": "Per-pallet length in inches (defaults to 48)",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / width_in
      Added value: +{
+  "description": "Per-pallet width in inches (defaults to 40)",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the safety profile is covered. The description adds 'firm price' and the 1-3 pallet scope, which are useful behavioral details, but does not explain what happens outside those bounds or describe the quote's return characteristics.

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?

A single, front-loaded sentence with no filler. It communicates the core action and key constraints immediately.

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 11 parameters fully documented in the schema and readOnlyHint covering safety, the description is minimally adequate. However, for a quote tool with no output schema, it does not clarify return format or how it relates to other quote modes, leaving some contextual gaps.

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?

Schema description coverage is 100%, so the schema already documents all 11 parameters. The description only mentions the pallet range, which is already defined in the schema, so it adds no meaningful parameter semantics beyond what is structured.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Quote') and resource ('cargo van shipment'), and adds scope ('1-3 pallets, firm price'). It distinguishes the tool from other quote siblings by mode, but does not explicitly name or contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/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 of 1-3 pallets, but offers no explicit when-to-use guidance or mention of alternative quote tools (e.g., ltl_quote, ftl_quote). An agent must infer the appropriate context from the mode name and constraints.

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
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.

Resources