Skip to main content
Glama

SMKlog Parcel Shipping Rates

Get live parcel shipping rates from a US origin

get_parcel_quote
Read-only

Live shipping rates for one parcel sent from a US origin — inside the US, or to Canada, the UK, Germany or Australia — across USPS, UPS and FedEx, and DHL Express on the German and Australian lanes. Describe the item in plain words and the packed box size and weight are estimated. Give exact dimensions and weight to skip the estimate. Returns up to five purchasable services, each as one checkout total with the SMKlog fee inside it (the fee is itemized only on the checkout receipt) and, where the carrier publishes one, its own counter price for the same parcel beside it.

Manual review: oversized, palletized or crated shipments are priced by a person. Clients that declare the io.modelcontextprotocol/tasks extension get a durable task handle (poll it with tasks/get, answers usually take a few business hours). Others get a pointer to the human review page. Shipping labels are bought on smklog.com, not through this tool.

Choosing between the tools: use this one to answer what a shipment would cost. Then hand the quote_id it returns to create_checkout_link once the human has settled on shipping this exact parcel, so the pair costs one carrier call rather than two. Use get_price_index instead for typical or historical prices: it is free, while this tool spends a rate-limited carrier call every time.

Parameter rules:

  • weight_lb, length_in, width_in and height_in count only as a set of four, each above zero. Leave any one out and all four are ignored in favor of the estimate, so never send weight alone.

  • Online pricing covers one parcel up to 150 lb, 108 in on the longest side and 165 in of length plus girth. A heavier or larger box, a quantity above 1, or a product worded as freight (pallet, LTL, truckload, machinery, bulk) returns no rates and goes to a person.

  • product is the item itself, up to 200 characters. A bare route ("to Canada"), a bare weight ("7 lbs") or a question is refused as product_not_recognized before any carrier is called.

  • from_zip must be a real 5-digit US ZIP (ZIP+4 is trimmed to five), or the call fails with invalid_us_zip.

  • to_zip follows to_country: a 5-digit ZIP for US, otherwise that country's own postal code handed to the carriers as typed. A to_country outside US, CA, GB, DE and AU is refused as international_unsupported_online, so do not retry it with a different box.

  • Allowance: 80 calls an hour per client, shared with the public /quote route.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_zipYesDestination postal code: a 5-digit ZIP for the US, or the destination country's own postal code, e.g. M5V 2T6 for Toronto or SW1A 1AA for London.
productYesPlain-words item description, e.g. "65 inch flat screen TV in original box".
from_zipYesOrigin US ZIP code, 5 digits. The origin is always in the United States.
quantityNoIdentical parcels in this shipment. Default 1.
width_inNoPacked box width, inches.
height_inNoPacked box height, inches.
length_inNoPacked box length, inches.
weight_lbNoPacked weight, pounds. Decimals allowed.
to_countryNoTwo-letter destination country: US (default), CA, GB, DE, AU.US

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoQuote mode; "freight_manager" routes to a human review
ratesYesUp to five purchasable services. Not cheapest first: they are ranked by best value, each rate scored as its checkout total in cents plus 175 per business day of transit (30 days when the carrier quotes none), lowest score first, and a rate that publishes a carrier counter price may lead a near-tie within 50 cents or 2 percent. Sort by amount yourself when you want the cheapest.
packageNoThe packed box the rates were computed for
quote_idNoHandle to this quote, good for 15 minutes. Pass it to create_checkout_link as quote_id and that call spends no second carrier call. Null when no rate came back, or when the handle could not be stored.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / rates / items / properties / amount / description
      Previous value: -"Checkout total, USD"New value: +"Checkout total, USD, SMKlog fee inside"
    • removedOutput schema / properties / rates / items / properties / carrier_amount
      Removed value: -{
      -  "description": "Negotiated carrier cost, USD",
      -  "type": "number"
      -}
    • removedOutput schema / properties / rates / items / properties / service_fee
      Removed value: -{
      -  "description": "SMKlog fee, USD",
      -  "type": "number"
      -}
  2. Changed1 schema field changed
    • changedOutput schema / properties / rates / description
      Previous value: -"Purchasable services, cheapest first"New value: +"Up to five purchasable services. Not cheapest first: they are ranked by best value, each rate scored as its checkout total in cents plus 175 per business day of transit (30 days when the carrier quotes none), lowest score first, and a rate that publishes a carrier counter price may lead a near-tie within 50 cents or 2 percent. Sort by amount yourself when you want the cheapest."
  3. Changed1 schema field changed
    • changedOutput schema / properties / rates / items / properties / carrier / description
      Previous value: -"USPS, UPS or FedEx"New value: +"USPS, UPS, FedEx or DHL"
  4. Changed14 schema fields changed
    • changedInput schema / properties / from_zip / description
      Previous value: -"Origin 5-digit US ZIP. The origin is always in the United States; there is no lane that starts abroad."New value: +"Origin US ZIP code, 5 digits. The origin is always in the United States."
    • changedInput schema / properties / height_in / description
      Previous value: -"Packed box height in inches."New value: +"Packed box height, inches."
    • addedInput schema / properties / height_in / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / length_in / description
      Previous value: -"Packed box length in inches. Supply all three dimensions AND weight_lb to skip the estimate."New value: +"Packed box length, inches."
    • addedInput schema / properties / length_in / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / product / description
      Previous value: -"Plain-words item description, e.g. \"65 inch flat screen TV in original box\""New value: +"Plain-words item description, e.g. \"65 inch flat screen TV in original box\"."
    • changedInput schema / properties / quantity / description
      Previous value: -"How many identical parcels ship together, priced as separate labels. Defaults to 1."New value: +"Identical parcels in this shipment. Default 1."
    • changedInput schema / properties / to_country / description
      Previous value: -"Two-letter destination country. Omit for a domestic shipment. Sold online: US, CA, GB, DE, AU. Any other country is refused with international_unsupported_online rather than priced, so do not retry it with a different box."New value: +"Two-letter destination country: US (default), CA, GB, DE, AU."
    • addedInput schema / properties / to_country / enum
      Added value: +[
      +  "US",
      +  "CA",
      +  "GB",
      +  "DE",
      +  "AU"
      +]
    • changedInput schema / properties / to_zip / description
      Previous value: -"Destination postal code. A 5-digit ZIP when to_country is US or omitted; otherwise that country's own postal code, e.g. M5V 2T6 for Toronto or SW1A 1AA for London."New value: +"Destination postal code: a 5-digit ZIP for the US, or the destination country's own postal code, e.g. M5V 2T6 for Toronto or SW1A 1AA for London."
    • changedInput schema / properties / weight_lb / description
      Previous value: -"Packed weight in pounds. Optional; estimated from the description when omitted."New value: +"Packed weight, pounds. Decimals allowed."
    • addedInput schema / properties / weight_lb / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / width_in / description
      Previous value: -"Packed box width in inches."New value: +"Packed box width, inches."
    • addedInput schema / properties / width_in / exclusiveMinimum
      Added value: +0
  5. Changed1 schema field changed
    • addedOutput schema / properties / quote_id
      Added value: +{
      +  "description": "Handle to this quote, good for 15 minutes. Pass it to create_checkout_link as quote_id and that call spends no second carrier call. Null when no rate came back, or when the handle could not be stored.",
      +  "type": "string"
      +}
  6. Changed4 schema fields changed
    • changedInput schema / properties / from_zip / description
      Previous value: -"Origin 5-digit US ZIP"New value: +"Origin 5-digit US ZIP. The origin is always in the United States; there is no lane that starts abroad."
    • changedInput schema / properties / quantity / description
      Previous value: -"How many identical parcels ship together. Defaults to 1."New value: +"How many identical parcels ship together, priced as separate labels. Defaults to 1."
    • addedInput schema / properties / to_country
      Added value: +{
      +  "default": "US",
      +  "description": "Two-letter destination country. Omit for a domestic shipment. Sold online: US, CA, GB, DE, AU. Any other country is refused with international_unsupported_online rather than priced, so do not retry it with a different box.",
      +  "type": "string"
      +}
    • changedInput schema / properties / to_zip / description
      Previous value: -"Destination 5-digit US ZIP"New value: +"Destination postal code. A 5-digit ZIP when to_country is US or omitted; otherwise that country's own postal code, e.g. M5V 2T6 for Toronto or SW1A 1AA for London."
  7. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and idempotentHint=false. The description adds substantial behavioral context: it spends a rate-limited carrier call, returns up to five purchasable services, includes the SMKlog fee in the total, surfaces a human-review path for nonstandard shipments, and documents the 80-calls/hour allowance. No contradiction 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?

Long but densely informative, organized into clear sections: overview, manual review, tool selection, and parameter rules. The core purpose is front-loaded in the first sentence. Every paragraph and bullet adds distinct operational value such that trimming would reduce correctness.

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?

Given the tool's complexity (9 params, live carrier calls, manual review fallback, sibling differentiation, rate limits) and the presence of an output schema, the description covers all necessary decision points. It even describes return shape (up to five checkout totals, fee inclusion, counter price) and error behavior, leaving no major gap for an agent invoking it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description goes far beyond the schema by explaining the all-or-nothing set rule for dimensions, the 150 lb / 108 in / 165 in limits, that quantity above 1 routes to manual review, that product should be the item itself and not a route/weight/question, ZIP normalization, and country-specific to_zip behavior. These are essential for correct invocation and are absent from the schema alone.

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 ('Get live parcel shipping rates'), resource ('one parcel sent from a US origin'), and scope (carriers, destination countries). Immediately distinguishes itself from siblings via the 'Choosing between the tools' section, so an agent can tell it apart from create_checkout_link and get_price_index.

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 when to use this tool ('to answer what a shipment would cost'), when to use create_checkout_link (after a human settles, to reuse the quote_id), and when to use get_price_index (typical/historical prices, free). Also specifies exclusions: oversized/freight shipments go to manual review, and unsupported countries are refused.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.9/5.0
Disambiguation5/5

Each tool targets a distinct operation: live quote versus checkout session versus reference index versus tracking. The only potential overlap is create_checkout_link's live-pricing fallback, but its stated purpose and required quote_id flow make the boundary clear.

Naming Consistency5/5

All four tool names follow the same imperative verb_noun pattern in snake_case: create_checkout_link, get_parcel_quote, get_price_index, track_parcel. No mixed conventions or vague verbs.

Tool Count5/5

Four tools is a well-scoped set for a parcel shipping domain: one for quotes, one for checkout links, one for reference pricing, and one for tracking. Each tool earns its place without bloat or redundancy.

Completeness4/5

The core workflow is covered: get a quote, create a checkout link, and track the resulting label, with a free price-index tool for reference. Minor gaps exist around post-purchase lifecycle operations like voiding labels or retrieving session status, but those are not central to the stated purpose.