warp-agent-mcp

Get International Rates (Air / Ocean)

international_quote

Read-only

Air, ocean and US / Mexico cross-border truck rates for a shipment with at least one end outside the US / Canada (import, export, or between two other countries). Describe the cargo ONE way: items (pallets / pieces with dimensions), containers (ocean full container load: 20'DV, 40'DV, 40'HC), or volume (total cubic feet when piece sizes are unknown). Returns every option: mode (AIR / OCEAN / TRUCK), service (LCL, FCL, STANDARD, EXPRESS, ...), door service (door_to_door, door_to_port, port_to_door), price, transit days, ports and how long the rate is valid. door_to_port and port_to_door prices do NOT include charges at the far port; tell the user that plainly, and the user must accept those charges before booking. Not served: hazardous materials, sanctioned countries, and pickup and delivery in the same non-US country. Pricing runs live and can take up to a minute; if it times out, retry once. For domestic US freight use compare_modes or ltl_quote instead. Book the user's chosen option with international_book. Requires a signed-in Warp account.

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": {
      "pickup_date": "<pickup_date>",
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "international_quote"
  }
}

Input Schema

Name	Required	Description
`items`	No	Pallets / pieces, one entry per group of identical units. Use this OR containers OR volume.
`origin`	Yes	Pickup location
`volume`	No	Loose cargo by total volume when piece sizes are unknown. Use this OR items OR containers.
`containers`	No	Ocean full container load (FCL), up to 30 containers. Use this OR items OR volume.
`destination`	Yes	Delivery location
`pickup_date`	Yes	YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedOct 30, 2026

addedInput schema / properties / containers

Added value: +{
+  "description": "Ocean full container load (FCL), up to 30 containers. Use this OR items OR volume.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "commodity": {
+        "description": "What is in them, e.g. 'Furniture'",
+        "type": "string"
+      },
+      "count": {
+        "description": "Number of containers of this size",
+        "minimum": 1,
+        "type": "integer"
+      },
+      "size": {
+        "description": "Container size: 20'DV, 40'DV or 40'HC (high cube)",
+        "enum": [
+          "20'DV",
+          "40'DV",
+          "40'HC"
+        ],
+        "type": "string"
+      },
+      "weight_lbs": {
+        "description": "Cargo weight per container, lb (max 67,200)",
+        "exclusiveMinimum": 0,
+        "maximum": 67200,
+        "type": "number"
+      }
+    },
+    "required": [
+      "size",
+      "count",
+      "commodity",
+      "weight_lbs"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}

removedInput schema / properties / destination / properties / city / $ref
```
Removed value: -"#/properties/origin/properties/city"
```
addedInput schema / properties / destination / properties / city / description
```
Added value: +"City. Needed outside the US / Canada."
```
addedInput schema / properties / destination / properties / city / type
```
Added value: +"string"
```
removedInput schema / properties / destination / properties / country / $ref
```
Removed value: -"#/properties/origin/properties/country"
```
addedInput schema / properties / destination / properties / country / description
```
Added value: +"ISO 3166-1 alpha-2 country code, e.g. US, CN, DE"
```
addedInput schema / properties / destination / properties / country / pattern
```
Added value: +"^[A-Za-z]{2}$"
```
addedInput schema / properties / destination / properties / country / type
```
Added value: +"string"
```
removedInput schema / properties / destination / properties / latitude / $ref
```
Removed value: -"#/properties/origin/properties/latitude"
```
addedInput schema / properties / destination / properties / latitude / description
```
Added value: +"Latitude, improves pricing outside the US / Canada"
```
addedInput schema / properties / destination / properties / latitude / type
```
Added value: +"number"
```
removedInput schema / properties / destination / properties / longitude / $ref
```
Removed value: -"#/properties/origin/properties/longitude"
```
addedInput schema / properties / destination / properties / longitude / description
```
Added value: +"Longitude"
```
addedInput schema / properties / destination / properties / longitude / type
```
Added value: +"number"
```
removedInput schema / properties / destination / properties / state / $ref
```
Removed value: -"#/properties/origin/properties/state"
```
addedInput schema / properties / destination / properties / state / description
```
Added value: +"State / province / region"
```
addedInput schema / properties / destination / properties / state / type
```
Added value: +"string"
```
removedInput schema / properties / destination / properties / street / $ref
```
Removed value: -"#/properties/origin/properties/street"
```
addedInput schema / properties / destination / properties / street / description
```
Added value: +"Street address"
```
addedInput schema / properties / destination / properties / street / type
```
Added value: +"string"
```
removedInput schema / properties / destination / properties / zipcode / $ref
```
Removed value: -"#/properties/origin/properties/zipcode"
```

addedInput schema / properties / destination / properties / zipcode / description

Added value: +"Postal code. Required where the country uses one (see international_settings)."

addedInput schema / properties / destination / properties / zipcode / type
```
Added value: +"string"
```

changedInput schema / properties / items / description

Previous value: -"One entry per group of identical pallets / pieces"New value: +"Pallets / pieces, one entry per group of identical units. Use this OR containers OR volume."

addedInput schema / properties / volume

Added value: +{
+  "additionalProperties": false,
+  "description": "Loose cargo by total volume when piece sizes are unknown. Use this OR items OR containers.",
+  "properties": {
+    "description": {
+      "description": "What it is, e.g. 'Furniture'",
+      "type": "string"
+    },
+    "max_height_in": {
+      "description": "Height of the tallest piece, inches",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "pieces": {
+      "description": "Number of pieces, if known",
+      "minimum": 1,
+      "type": "integer"
+    },
+    "total_cubic_ft": {
+      "description": "Total volume of the shipment, cubic feet (max ~5,300 / 150 m3)",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "total_weight_lbs": {
+      "description": "Total weight of the shipment, lb",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_cubic_ft",
+    "max_height_in",
+    "total_weight_lbs"
+  ],
+  "type": "object"
+}

changedInput schema / required

Previous value: -[
-  "pickup_date",
-  "origin",
-  "destination",
-  "items"
-]New value: +[
+  "pickup_date",
+  "origin",
+  "destination"
+]

AddedOct 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries real weight: live pricing can take up to a minute, retry once on timeout, requires a signed-in Warp account. Most valuable is the disclosure that door_to_port and port_to_door prices exclude far-port charges and that the user must accept those charges before booking — a behavioral fact not derivable from any structured field.

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?

One dense paragraph, but front-loaded with scope and cargo-mode rule, then returns, then the door-charge caveat, then exclusions, then operational timing, then alternatives and booking. Every sentence supplies information an agent would otherwise have to guess.

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?

No output schema exists, yet the description enumerates the returned fields (mode, service, door service, price, transit days, ports, rate validity), which is exactly what the agent needs to present results. Combined with the mutually exclusive payload rule, exclusions, latency behavior and the downstream booking tool, nothing material is missing for a 6-parameter nested-input tool.

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; the description earns credit by stating the mutually exclusive cargo-description constraint up front ('Describe the cargo ONE way') and naming the container sizes, which helps the agent pick the right branch before reading nested schemas. The per-branch hints (volume when piece sizes are unknown) are largely duplicated by the schema's own 'Use this OR...' descriptions, so it stops short of a 5.

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?

States specific verbs and resources: air, ocean and US/Mexico cross-border truck rates, with the scoping rule that at least one end must be outside the US/Canada. It also names what it is not (domestic US freight), so an agent can separate it from compare_modes, ltl_quote and the parcel/van/FTL quote siblings without opening a schema.

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?

Explicit routing: 'For domestic US freight use compare_modes or ltl_quote instead' and 'Book the user's chosen option with international_book.' It also gives negative cases — hazmat, sanctioned countries, and same-non-US-country pickup/delivery are not served — plus the timeout/retry-once procedure.

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.