Packrift MCP

Prepare purchase handoff

prepare_purchase_handoff

Read-onlyIdempotent

Two-step exact-SKU purchase prep. Call first with sku, quantity, and buyer_confirmed=false to confirm the product, live price, and live stock in one call. After the buyer approves, call again with buyer_confirmed=true to receive the tracked checkout handoff URL. It never places an order.

Input Schema

TableJSON Schema

Name	Required	Description
`sku`	Yes	Exact Packrift SKU such as 1066, MFL1295, or LL251WR.
`quantity`	No	Buyer-selected quantity. Defaults to 1.
`journey_id`	No	Optional continuity ID echoed from an earlier search or pricing result in this conversation.
`result_set_id`	No	Optional continuity ID echoed from the result set the buyer chose from.
`source_context`	No	Optional short context label for the handoff, such as exact_sku_reorder or quote_followup.
`buyer_confirmed`	No	Set true only after the buyer confirms the exact SKU and quantity. Without this, no cart URL is created.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedJul 31, 2026

removedInput schema / properties / analytics_context

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

addedInput schema / properties / journey_id / description

Added value: +"Optional continuity ID echoed from an earlier search or pricing result in this conversation."

removedInput schema / properties / mcp_install_target

Removed value: -{
-  "description": "Optional install target for source-aware MCP installs, such as cline, codex, or generic_streamable_http.",
-  "type": "string"
-}

removedInput schema / properties / mcp_source
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / mcp_source_context

Removed value: -{
-  "description": "Optional source slug for source-aware MCP installs, such as cline_mcp_marketplace or mcp_so.",
-  "type": "string"
-}

removedInput schema / properties / mcp_target
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / packrift_mcp_source
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / packrift_mcp_target
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / result_set_id / description

Added value: +"Optional continuity ID echoed from the result set the buyer chose from."

changedInput schema / properties / source_context / description

Previous value: -"Optional analytics context, such as agent_quick_start, exact_sku_reorder, or browse_sh_first_cart_run."New value: +"Optional short context label for the handoff, such as exact_sku_reorder or quote_followup."

removedInput schema / properties / source_slug
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / suppress_analytics

Removed value: -{
-  "description": "Internal QA flag. When true, do not record downstream cart analytics.",
-  "type": "boolean"
-}

AddedMay 25, 2026
RemovedMay 25, 2026

Changed14 schema fields changedMay 23, 2026

removedInput schema / additionalProperties
```
Removed value: -true
```

addedInput schema / properties / analytics_context

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

changedInput schema / properties / buyer_confirmed / description

Previous value: -"Set true only after the buyer confirms the exact SKU and quantity. Without this, no cart URL is returned."New value: +"Set true only after the buyer confirms the exact SKU and quantity. Without this, no cart URL is created."

addedInput schema / properties / journey_id
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / mcp_install_target

Added value: +{
+  "description": "Optional install target for source-aware MCP installs, such as cline, codex, or generic_streamable_http.",
+  "type": "string"
+}

addedInput schema / properties / mcp_source
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / mcp_source_context

Added value: +{
+  "description": "Optional source slug for source-aware MCP installs, such as cline_mcp_marketplace or mcp_so.",
+  "type": "string"
+}

addedInput schema / properties / mcp_target
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / packrift_mcp_source
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / packrift_mcp_target
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / result_set_id
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / source_context

Added value: +{
+  "description": "Optional analytics context, such as agent_quick_start, exact_sku_reorder, or browse_sh_first_cart_run.",
+  "type": "string"
+}

addedInput schema / properties / source_slug
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / suppress_analytics

Added value: +{
+  "description": "Internal QA flag. When true, do not record downstream cart analytics.",
+  "type": "boolean"
+}

Changed14 schema fields changedMay 22, 2026

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

removedInput schema / properties / analytics_context

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

changedInput schema / properties / buyer_confirmed / description

Previous value: -"Set true only after the buyer confirms the exact SKU and quantity. Without this, no cart URL is created."New value: +"Set true only after the buyer confirms the exact SKU and quantity. Without this, no cart URL is returned."

removedInput schema / properties / journey_id
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / mcp_install_target

Removed value: -{
-  "description": "Optional install target for source-aware MCP installs, such as cline, codex, or generic_streamable_http.",
-  "type": "string"
-}

removedInput schema / properties / mcp_source
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / mcp_source_context

Removed value: -{
-  "description": "Optional source slug for source-aware MCP installs, such as cline_mcp_marketplace or mcp_so.",
-  "type": "string"
-}

removedInput schema / properties / mcp_target
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / packrift_mcp_source
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / packrift_mcp_target
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / result_set_id
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / source_context

Removed value: -{
-  "description": "Optional analytics context, such as agent_quick_start, exact_sku_reorder, or browse_sh_first_cart_run.",
-  "type": "string"
-}

removedInput schema / properties / source_slug
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / suppress_analytics

Removed value: -{
-  "description": "Internal QA flag. When true, do not record downstream cart analytics.",
-  "type": "boolean"
-}

Changed7 schema fields changedMay 20, 2026

addedInput schema / properties / mcp_install_target

Added value: +{
+  "description": "Optional install target for source-aware MCP installs, such as cline, codex, or generic_streamable_http.",
+  "type": "string"
+}

addedInput schema / properties / mcp_source
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / mcp_source_context

Added value: +{
+  "description": "Optional source slug for source-aware MCP installs, such as cline_mcp_marketplace or mcp_so.",
+  "type": "string"
+}

addedInput schema / properties / mcp_target
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / packrift_mcp_source
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / packrift_mcp_target
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / source_slug
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedMay 20, 2026

changedInput schema / properties / source_context / description

Previous value: -"Optional analytics context, such as agent_quick_start, exact_sku_reorder, or browserbase_browse."New value: +"Optional analytics context, such as agent_quick_start, exact_sku_reorder, or browse_sh_first_cart_run."

AddedMay 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint), the description discloses key behavioral traits: it never places an order, it confirms live price and stock, and it requires a two-step confirmation process. This adds meaningful context that is not captured by annotations alone, helping the agent understand the side effects and state involved.

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 concise and front-loaded with the core purpose ('Two-step exact-SKU purchase prep'). It then explains the two-step flow in two clear sentences and ends with a boundary condition ('It never places an order'). Every sentence earns its place without redundancy.

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 tool has moderate complexity with a two-step flow and no output schema, so the description carries the burden of explaining return behavior. It mentions the outcome ('tracked checkout handoff URL') and implies the first response includes product, live price, and stock. However, it doesn't explicitly describe the exact structure of the first response or possible error conditions, leaving a slight gap. Still, it is sufficiently complete for an agent to use the tool correctly.

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?

The input schema already provides 100% coverage with descriptions for all six parameters, so the baseline is 3. The description adds a bit of context by explaining the role of buyer_confirmed in the two-step flow, but it does not add significant new semantics beyond what the schema already states. It reinforces the purpose of key parameters but does not compensate for any gaps.

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 clearly states the tool's function: 'Two-step exact-SKU purchase prep.' It specifies the verb ('prepare') and the resource ('purchase handoff'), and distinguishes itself from siblings by emphasizing the exact-SKU and two-step nature. The explicit statement 'It never places an order' further clarifies its scope, separating it from order-placing tools.

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?

The description provides explicit step-by-step usage instructions: call first with buyer_confirmed=false to confirm product/price/stock, then call again with buyer_confirmed=true to receive the handoff URL. It also clarifies that no order is placed. While it doesn't explicitly name alternative tools, the two-step flow and confirmation requirement give clear context for when this tool is appropriate.

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.

Prepare purchase handoff

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources