Packrift MCP

Get shipping estimate

get_shipping_estimate

Read-only

Use when the buyer asks shipping cost for selected catalog variants. Provide destination_address with address1, city and province_code for an estimate using the supplied address; otherwise the estimate uses postal-code placeholders and is approximate. Addresses are not validated. Cart shipping discounts and final tax are not evaluated; Shopify cart and checkout are authoritative. Required arguments: destination_postal_code, country (US|CA), and items with variant_id as a numeric Shopify variant ID string plus qty, for example {"variant_id":"53475949216112","qty":1}. Never send variant_id as a number.

Input Schema

TableJSON Schema

Name	Required	Description
`items`	Yes
`country`	Yes
`journey_id`	No
`match_type`	No
`selected_sku`	No
`result_set_id`	No
`selected_handle`	No
`destination_address`	No	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.
`destination_postal_code`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.6/5.0

Behavior5/5

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

Annotations already mark it read-only, and the description adds important behavioral details: addresses are not validated, cart discounts and tax are not evaluated, and the estimate may be approximate when using placeholders. It also warns about variant_id type. This goes beyond the annotations and helps the agent set expectations.

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, information-dense paragraph that front-loads the usage condition and then covers key behaviors and requirements. Every sentence adds value; there is no filler. It could be slightly more structured, but it's efficient.

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

Completeness4/5

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

The description covers the core functionality, required parameters, address behavior, and limitations. Since there is no output schema, it would be helpful to state the return format (e.g., a numeric estimate or object), but this is a minor gap. The description is largely sufficient for an agent to call the tool correctly.

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?

With only 11% schema coverage, the description compensates by explaining the required arguments and the behavior of the destination_address object. It clarifies the variant_id string requirement and provides an example. Optional parameters like journey_id are not explained, but they are likely secondary. The description covers the critical parameters.

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 opens with a clear trigger condition ('Use when the buyer asks shipping cost for selected catalog variants') and specifies the resource (shipping estimate). It clearly distinguishes from pricing or inventory tools by focusing on shipping cost. The scope is well-defined.

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?

It explicitly states when to use (buyer asks shipping cost for selected variants) and provides conditional guidance on providing destination_address. It also sets expectations that the estimate is approximate without full address and that Shopify cart/checkout are authoritative, implying when not to rely solely on this tool. It doesn't name alternative tools explicitly but gives sufficient context.

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.

Get shipping estimate

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources