Packrift MCP

Estimate delivered cost of a Packrift order

get_shipping_estimate

Read-onlyIdempotent

Estimate the delivered cost of a Packrift order to a US ZIP code, using the same shipping rates and automatic volume discounts as Packrift checkout. Give the items as SKU and quantity (number of packs). Returns the subtotal after discounts, the shipping charge (free only when the order qualifies), the delivered total and the delivered cost per unit. Tax is not included; checkout shows the final amount. Not for carrier rate shopping or postage.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	Items to price.
`response_format`	No	concise (default) returns the essentials. detailed returns the full catalog record; use it only when a field you need is missing.	concise
`destination_state`	No	Optional two-letter state code, e.g. "TX", for a more precise estimate.
`destination_postal_code`	Yes	US delivery ZIP code, e.g. "75201".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	No
`shipping_options`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "items": {
+      "type": "array"
+    },
+    "shipping_options": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed19 schema fields changedSep 27, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / country

Removed value: -{
-  "enum": [
-    "US",
-    "CA"
-  ],
-  "type": "string"
-}

removedInput schema / properties / destination_address

Removed value: -{
-  "additionalProperties": false,
-  "description": "Optional address details used with destination_postal_code and country. Supply all three fields or omit this object. Values are passed through, not address-validated.",
-  "properties": {
-    "address1": {
-      "minLength": 1,
-      "type": "string"
-    },
-    "city": {
-      "minLength": 1,
-      "type": "string"
-    },
-    "province_code": {
-      "description": "State or province code, for example WI or ON.",
-      "minLength": 1,
-      "type": "string"
-    }
-  },
-  "required": [
-    "address1",
-    "city",
-    "province_code"
-  ],
-  "type": "object"
-}

addedInput schema / properties / destination_postal_code / description
```
Added value: +"US delivery ZIP code, e.g. \"75201\"."
```

addedInput schema / properties / destination_state

Added value: +{
+  "description": "Optional two-letter state code, e.g. \"TX\", for a more precise estimate.",
+  "type": "string"
+}

addedInput schema / properties / items / description
```
Added value: +"Items to price."
```

removedInput schema / properties / items / items / properties / qty

Removed value: -{
-  "description": "Quantity for this line item. The alias key quantity is also accepted.",
-  "minimum": 1,
-  "type": "integer"
-}

addedInput schema / properties / items / items / properties / quantity

Added value: +{
+  "description": "Number of packs.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / items / items / properties / sku

Added value: +{
+  "description": "Packrift SKU.",
+  "type": "string"
+}

removedInput schema / properties / items / items / properties / variant_id

Removed value: -{
-  "description": "Numeric Shopify variant ID as a string, not a number. Example: \"53475949216112\".",
-  "type": "string"
-}

changedInput schema / properties / items / items / required

Previous value: -[
-  "variant_id",
-  "qty"
-]New value: +[
+  "sku",
+  "quantity"
+]

addedInput schema / properties / items / maxItems
```
Added value: +25
```
removedInput schema / properties / journey_id
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / match_type
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / response_format

Added value: +{
+  "default": "concise",
+  "description": "concise (default) returns the essentials. detailed returns the full catalog record; use it only when a field you need is missing.",
+  "enum": [
+    "concise",
+    "detailed"
+  ],
+  "type": "string"
+}

removedInput schema / properties / result_set_id
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / selected_handle
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / selected_sku
```
Removed value: -{
-  "type": "string"
-}
```

changedInput schema / required

Previous value: -[
-  "destination_postal_code",
-  "country",
-  "items"
-]New value: +[
+  "destination_postal_code",
+  "items"
+]

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / destination_address

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional address details used with destination_postal_code and country. Supply all three fields or omit this object. Values are passed through, not address-validated.",
+  "properties": {
+    "address1": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "city": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "province_code": {
+      "description": "State or province code, for example WI or ON.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "address1",
+    "city",
+    "province_code"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 12, 2026

changedInput schema / properties / items / items / properties / qty / description

Previous value: -"Quantity for this line item."New value: +"Quantity for this line item. The alias key quantity is also accepted."

Changed2 schema fields changedMay 25, 2026
- addedInput schema / properties / items / items / properties / qty / description
```
Added value: +"Quantity for this line item."
```
- addedInput schema / properties / items / items / properties / variant_id / description
```
Added value: +"Numeric Shopify variant ID as a string, not a number. Example: \"53475949216112\"."
```
Changed2 schema fields changedMay 25, 2026
- removedInput schema / properties / items / items / properties / qty / description
```
Removed value: -"Quantity for this line item."
```
- removedInput schema / properties / items / items / properties / variant_id / description
```
Removed value: -"Numeric Shopify variant ID as a string, not a number. Example: \"53475949216112\"."
```
Changed2 schema fields changedMay 24, 2026
- addedInput schema / properties / items / items / properties / qty / description
```
Added value: +"Quantity for this line item."
```
- addedInput schema / properties / items / items / properties / variant_id / description
```
Added value: +"Numeric Shopify variant ID as a string, not a number. Example: \"53475949216112\"."
```
Changed5 schema fields changedMay 7, 2026
- addedInput schema / properties / journey_id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / match_type
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / result_set_id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / selected_handle
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / selected_sku
```
Added value: +{
+  "type": "string"
+}
```
First observedApr 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world, so the safety profile is largely covered. The description adds genuine behavioral context beyond that: discounts are applied automatically, shipping is free only when the order qualifies, and tax is excluded. Return shape is also summarized, though no rate limits or failure modes are mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, followed by input format, return fields, and limits. Every sentence carries information, though the enumeration of returned fields is slightly list-like. No filler or redundancy.

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?

An output schema exists and the description still summarizes the key returned values (discounted subtotal, shipping charge, delivered total, per-unit cost). Combined with annotations covering safety and idempotency, and the schema covering inputs, an agent has everything needed to call this correctly and interpret the result.

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 every parameter is already documented in the schema, and the description adds little syntax beyond restating that items are SKU + quantity (number of packs). The response_format tradeoff (concise vs detailed) is explained in the schema rather than the description. Baseline 3 is appropriate when the schema carries the parameter burden.

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 a specific verb (Estimate) plus the exact resource (delivered cost of a Packrift order to a US ZIP), and immediately scopes it with 'using the same shipping rates and automatic volume discounts as Packrift checkout.' It also distinguishes itself from adjacent concerns by excluding carrier rate shopping and postage, so an agent can tell it apart from siblings like get_product or create_cart_url.

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?

Clearly signals when to use it (pre-checkout delivered-cost estimation against real Packrift rates) and adds an explicit exclusion ('Not for carrier rate shopping or postage'). It also warns that tax is excluded and checkout shows the final amount. It stops short of naming a sibling alternative for the checkout/final-amount case, so it is clear context without full when-not routing.

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

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