Skip to main content
Glama

Packrift MCP

by io.github.Packrift

Find packaging for an item

find_packaging_for_item
Read-onlyIdempotent

Use when the buyer has item dimensions and needs a fitting box or mailer. Required arguments are item_length_in, item_width_in, item_depth_in, item_weight_lb, and use_case. Canonical use_case values are mailer|box|fragile|apparel|ecommerce; free text such as 'shipping ceramic mugs' is accepted and mapped to the closest canonical context. Returns up to 5 curated SKUs ranked by fit with price, stock, URL, and cart-continuity fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
use_caseYesPackaging context that guides fit ranking. Canonical values: mailer, box, fragile, apparel, ecommerce. Free text (e.g. 'shipping ceramic mugs') is accepted and mapped to the closest canonical context.
item_depth_inYesItem depth/height in inches.
item_width_inYesItem width in inches.
item_length_inYesItem length in inches.
item_weight_lbYesPacked item weight in pounds; use 0 when unknown.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds valuable behavioral context by specifying the output: 'Returns up to 5 curated SKUs ranked by fit with price, stock, URL, and cart-continuity fields.' It also clarifies free-text use_case handling. No contradictions with annotations.

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 two sentences, front-loaded with the primary use case, then details requirements and output. Every sentence adds functional information with no redundancy or fluff.

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?

Although there is no output schema, the description compensates by naming the return fields (price, stock, URL, cart-continuity) and the result limit of 5 SKUs. It also explains input requirements and use_case mapping. It does not cover edge cases like no-match behavior, but sibling tools (explain_no_exact_match) suggest that gap is intentionally handled elsewhere.

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% for all five parameters, so the baseline is 3. The description lists required arguments and reiterates use_case canonical values, but adds little beyond the schema's existing parameter descriptions. It does not introduce any new parameter-level semantics.

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 purpose: finding packaging (box or mailer) for an item based on dimensions. It uses a specific verb ('find') and resource ('packaging'), and distinguishes it from siblings like search_products or pack_calculator by focusing on the buyer's dimensions and need.

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?

The opening phrase 'Use when the buyer has item dimensions and needs a fitting box or mailer' explicitly defines the trigger condition. It also explains how use_case values are canonicalized, giving the agent clear guidance on input preparation.

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

All Packrift MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools have overlapping purposes: check_inventory and inventory_status both focus on live stock, find_packaging_for_item and pack_calculator both handle dimension-based fitting, and create_cart_url, prepare_purchase_handoff, and get_cart_handoff_candidates all revolve around cart handoff. While descriptions add some clarity, an agent could easily select the wrong tool without careful reading.

Naming Consistency4/5

Most tools follow a verb_noun pattern (e.g., check_inventory, get_pricing, search_products), but inventory_status and pack_calculator are noun-based and break the convention. The naming is still predictable and readable overall.

Tool Count4/5

15 tools is at the upper edge of the ideal range, and the count feels slightly inflated due to overlapping inventory and cart-handoff tools. However, each tool has a defined purpose in the procurement workflow, so the count is not excessive.

Completeness5/5

The tool surface covers the full buyer journey: search, fit calculation, comparison, product detail, inventory check, pricing, cart creation, purchase handoff, shipping estimates, quotes, and reorder links. No critical dead ends were found.

Resources