Packrift MCP

Request a bulk or custom quote

get_bulk_quote_link

Read-onlyIdempotent

Get a pre-filled quote request link for pallet or recurring quantities, custom sizes, printed or branded packaging, freight orders, or any spec Packrift does not stock exactly. Put everything the buyer told you in the fields: the spec, quantity, delivery ZIP and need-by date travel with the request. The buyer adds their email and submits the form on packrift.com; Packrift replies by email with pricing. Returns the link and what the buyer still needs to add.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sku`	No	A stocked Packrift SKU the request is for. Leave empty for custom, printed or branded packaging.
`quantity`	No	Quantity per order and how often, e.g. "5,000 per quarter".
`needed_by`	No	Date the buyer needs delivery, if known.
`delivery_zip`	No	US delivery ZIP code, if known.
`requested_spec`	Yes	What the buyer needs, e.g. "18x12x12 ECT-44 kraft boxes, printed 1 color on 2 sides". Include size, strength or thickness, color and any printing.
`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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`quote_url`	No
`requested_spec`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 27, 2026

addedInput schema / properties / delivery_zip

Added value: +{
+  "description": "US delivery ZIP code, if known.",
+  "type": "string"
+}

addedInput schema / properties / needed_by

Added value: +{
+  "description": "Date the buyer needs delivery, if known.",
+  "type": "string"
+}

changedInput schema / properties / quantity / description

Previous value: -"Quantity in units or packs, if known."New value: +"Quantity per order and how often, e.g. \"5,000 per quarter\"."

changedInput schema / properties / requested_spec / description

Previous value: -"What the buyer needs, e.g. \"2,000 18x12x12 ECT-44 boxes, printed 1 color\"."New value: +"What the buyer needs, e.g. \"18x12x12 ECT-44 kraft boxes, printed 1 color on 2 sides\". Include size, strength or thickness, color and any printing."

changedInput schema / properties / sku / description

Previous value: -"Related Packrift SKU, if any."New value: +"A stocked Packrift SKU the request is for. Leave empty for custom, printed or branded packaging."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "quote_url": {
+      "type": "string"
+    },
+    "requested_spec": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed7 schema fields changedSep 27, 2026

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

removedInput schema / properties / family

Removed value: -{
-  "description": "Optional product family such as boxes, labels, mailers, tape, or poly_bags.",
-  "type": "string"
-}

changedInput schema / properties / quantity / description

Previous value: -"Optional buyer quantity. Numbers are accepted and coerced to string."New value: +"Quantity in units or packs, if known."

removedInput schema / properties / reason

Removed value: -{
-  "description": "Optional reason for quote handoff.",
-  "type": "string"
-}

changedInput schema / properties / requested_spec / description

Previous value: -"Exact unavailable or bulk quote packaging spec."New value: +"What the buyer needs, e.g. \"2,000 18x12x12 ECT-44 boxes, printed 1 color\"."

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"
+}

changedInput schema / properties / sku / description

Previous value: -"Optional Packrift SKU to prefill if the quote relates to a known product."New value: +"Related Packrift SKU, if any."

Changed2 schema fields changedJul 31, 2026

removedInput schema / properties / analytics_context

Removed value: -{
-  "description": "Internal QA context for synthetic evals.",
-  "type": "object"
-}

removedInput schema / properties / suppress_analytics

Removed value: -{
-  "description": "Internal QA flag. When true, do not record an AI-sales quote event.",
-  "type": "boolean"
-}

Changed1 schema field changedJul 12, 2026

changedInput schema / properties / quantity / description

Previous value: -"Optional buyer quantity."New value: +"Optional buyer quantity. Numbers are accepted and coerced to string."

Changed2 schema fields changedMay 10, 2026

addedInput schema / properties / analytics_context

Added value: +{
+  "description": "Internal QA context for synthetic evals.",
+  "type": "object"
+}

addedInput schema / properties / suppress_analytics

Added value: +{
+  "description": "Internal QA flag. When true, do not record an AI-sales quote event.",
+  "type": "boolean"
+}

AddedMay 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavioral context beyond that: the link is pre-filled from the supplied fields, the buyer adds email and submits on packrift.com, and Packrift replies by email with pricing. It still doesn't state link lifetime or rate limits, but the workflow disclosure is substantial.

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?

Four tight sentences, front-loaded with the purpose before the field-completion instruction and the return explanation. No filler, though the closing return-value sentence is partly redundant given the output schema.

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?

For a read-only link builder with full schema coverage and an output schema, the description covers purpose, trigger conditions, how inputs are consumed, and the human handoff that follows. An agent has everything needed to call it correctly and explain the outcome to the user.

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 adds value by explaining that the supplied values are carried into the form ('the spec, quantity, delivery ZIP and need-by date travel with the request'), telling the agent these fields pre-fill the buyer's request rather than merely filtering a response.

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 and resource ('Get a pre-filled quote request link') and enumerates the exact scenarios it covers (pallet/recurring quantities, custom sizes, printed/branded packaging, freight, non-stocked specs), which clearly separates it from siblings like create_cart_url or get_shipping_estimate.

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?

Gives explicit when-to-use conditions ('any spec Packrift does not stock exactly'), so an agent knows to route here instead of product lookup tools. It does not name the sibling tools as alternatives, leaving that inference to the agent, which keeps it short of a 5.

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.

Request a bulk or custom quote

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources