Skip to main content
Glama

Packrift MCP

by io.github.Packrift
OverviewDiscussionsAdmin

Get bulk quote link

get_bulk_quote_link
Read-onlyIdempotent

Return a quote-request URL for an exact packaging spec or SKU. Use when no exact match exists or the buyer needs bulk or procurement review.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuNoOptional Packrift SKU to prefill if the quote relates to a known product.
familyNoOptional product family such as boxes, labels, mailers, tape, or poly_bags.
reasonNoOptional reason for quote handoff.
quantityNoOptional buyer quantity. Numbers are accepted and coerced to string.
requested_specYesExact unavailable or bulk quote packaging spec.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
-}
  2. Changed1 schema field changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Optional buyer quantity."New value: +"Optional buyer quantity. Numbers are accepted and coerced to string."
  3. Changed2 schema fields changed
    • 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"
+}
  4. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the context that it returns a URL and is intended for bulk/procurement review, but no additional behavioral details such as authentication or rate limits. This is adequate given the 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?

Two sentences, direct and front-loaded. The first sentence states the action and resource, the second gives the usage context. No redundant or filler content.

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?

Given the tool's simplicity, a 5-parameter schema with no output schema, the description sufficiently explains what it returns (a URL) and when to use it. It could mention how the URL should be used, but the purpose and usage are clear enough to invoke 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?

Schema description coverage is 100%, so every parameter is already well-documented. The description adds only marginal meaning by tying the purpose to 'exact packaging spec or SKU,' but it does not explain any parameter semantics beyond the schema. Baseline 3 is appropriate.

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 returns a quote-request URL for a packaging spec or SKU, and explicitly notes it is for cases with no exact match or bulk/procurement needs. This distinguishes it from sibling tools like get_product or search_products.

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 gives a clear 'when to use' condition: 'Use when no exact match exists or the buyer needs bulk or procurement review.' It does not explicitly name alternatives or provide a 'when not' clause, but the condition implies when not to use it.

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
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.

Resources