Skip to main content
Glama
smklog

SMKlog Parcel Shipping Rates

Get live parcel shipping rates from a US origin

get_parcel_quote
Read-only

Get live parcel shipping rates from a US origin to the US, Canada, UK, Germany, or Australia. Compare USPS, UPS, FedEx, and DHL Express prices with a plain-words item description.

Instructions

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 with the checkout total, the carrier cost beneath it and the SMKlog fee stated separately.

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
ratesYesPurchasable services, cheapest first
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.
Install Server

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark this read-only and non-destructive, and the description adds substantial behavioral context: dimension estimation behavior, purchasable-service return shape, manual review path, tasks extension behavior, label purchasing location, rate-limited carrier calls, and an 80-call hourly allowance. 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?

Although long, the description is tightly organized with labeled sections and every sentence carries operational value. The core behavior is front-loaded and the parameter rules are grouped logically rather than repeated.

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?

For a 9-parameter tool with rich validation, rate limits, carrier integration, and sibling routing, the description covers all necessary invocation details, error cases, and fallback paths. The output schema exists, so return-value documentation is not required from the description.

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%, yet the description still adds critical semantics: the four parcel-dimension parameters must be sent as a set or all are ignored, product is validated against bare routes/weights/questions, from_zip must be a real 5-digit ZIP, and to_zip semantics depend on to_country. This goes well beyond the schema.

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 names a specific verb and resource: getting live parcel shipping rates from a US origin, with explicit carriers and destination countries. It also distinguishes itself from get_price_index and create_checkout_link, so an agent can select it correctly without opening sibling schemas.

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 description explicitly says when to use this tool versus get_price_index, and instructs the agent to pass the returned quote_id to create_checkout_link. It also covers when a human is required (oversized, palletized, crated shipments), leaving no ambiguity about routing.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smklog/parcel-shipping-rates-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server