Packrift MCP

Get Packrift product details

get_product

Read-onlyIdempotent

Get one Packrift product by SKU (or product handle): specs such as inside size, material, strength and pack count, live price and price per unit, stock, whether a quantity can ship now, volume pricing, nearby sizes and the product link. Use after search_products or find_packaging_for_item when the buyer wants more detail before choosing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sku`	No	Packrift SKU, e.g. "1066".
`handle`	No	Product handle from a product URL, if you have it instead of a SKU.
`quantity`	No	Optional number of packs the buyer wants, to check it can ship now.
`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
`sku`	No
`url`	No
`specs`	No
`title`	No
`nearby_sizes`	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": {
+    "nearby_sizes": {
+      "type": "array"
+    },
+    "sku": {
+      "type": "string"
+    },
+    "specs": {
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed6 schema fields changedSep 27, 2026

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

addedInput schema / properties / handle / description

Added value: +"Product handle from a product URL, if you have it instead of a SKU."

addedInput schema / properties / quantity

Added value: +{
+  "description": "Optional number of packs the buyer wants, to check it can ship now.",
+  "minimum": 1,
+  "type": "integer"
+}

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

addedInput schema / properties / sku

Added value: +{
+  "description": "Packrift SKU, e.g. \"1066\".",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "handle"
-]
```

First observedApr 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavioral context: it returns live price, live stock, ship-now feasibility for a given quantity, and volume pricing. It does not cover failure behavior (e.g., unknown SKU, or neither identifier supplied).

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?

Two sentences, front-loaded with the identifier and the payoff, with the routing guidance second. The long field enumeration in sentence one is dense but all of it is informative rather than filler.

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?

An output schema exists, so return values need not be explained, yet the description summarizes them helpfully and routes the agent correctly. The one remaining gap is that zero parameters are required, and the description never says what to do if neither sku nor handle is available.

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, but the description adds meaning beyond the schema: it frames sku/handle as alternatives, explains that quantity exists to check whether that amount can ship now, and notes the product link is returned. It does not clarify the SKU-vs-handle precedence when both are passed.

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 one Packrift product by SKU (or product handle)') and enumerates the returned content area (specs, price, stock, volume pricing, link). It is clearly distinguishable from the sibling retrieval tools search_products and find_packaging_for_item, which it names.

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?

Explicitly says to use it 'after search_products or find_packaging_for_item when the buyer wants more detail before choosing,' naming both alternatives and the condition that selects this tool. The retrieval-then-detail sequencing is unambiguous.

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.