Skip to main content
Glama

International shipping cost from the US (live DHL/FedEx/UPS/USPS rates)

get_shipping_rates
Read-onlyIdempotent

Live shipping prices from Global Shopaholics' US warehouse (Delaware) to a destination country, for DHL, FedEx, UPS and USPS services. Returns each service's USD price, transit time, max weight/size, insurance terms and whether dimensional weight applies, sorted cheapest first. Prices exclude import duties/taxes. Use for 'how much does shipping from the USA to cost', 'cheapest courier to ship X kg to ', package forwarding prices and delivery time estimates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>",
      "weight": "<weight>"
    },
    "name": "get_shipping_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoDestination postal code. Defaults to the calculator's capital zip (00000 where none).
cityNoDestination city. Defaults to the capital GS's calculator uses.
unitNoUnit for weight. Dimensions use cm with kg, inches with lb.kg
widthNoBox width.
heightNoBox height.
lengthNoBox length (cm if kg, in if lb). Optional; improves accuracy because dimensional weight applies.
weightYesPackage weight (0.1–275 in the chosen unit; decimals OK). Use the expected consolidated box weight.
countryYesDestination country: ISO 2-letter code (AO, SA, AE, GB, NG...) or name ('Angola').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: results are sorted cheapest first, prices are USD and exclude duties/taxes, and each row includes transit time, weight/size limits, insurance terms and a dimensional-weight flag. It doesn't state rate validity or whether quotes are guaranteed, which is the only remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each carrying distinct information: source/scope, return contents, then exclusions and use cases. The warehouse location and carrier list are front-loaded. Slightly dense but no sentence is filler.

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?

With 8 parameters (6 of them optional dimensions/locale fields) and no output schema, the description usefully compensates by enumerating the returned fields and sort order. It is nearly complete, missing only quote validity/freshness and whether box dimensions can change the quoted price beyond the dim-weight flag.

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 documented in the input schema, including zip/city defaults, unit duality (cm/kg vs in/lb) and the dimensional-weight accuracy note for length. The description adds only the framing that weight can be quoted in kg for a consolidated box, which is marginal 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 ('Live shipping prices from Global Shopaholics' US warehouse (Delaware) to a destination country'), scopes the carriers (DHL, FedEx, UPS, USPS), and states the output shape. It is clearly distinguishable from siblings such as estimate_landed_cost or request_shipment_quote.

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?

It gives concrete triggering phrasings ('how much does shipping from the USA to <country> cost', 'cheapest courier to ship X kg to <country>', package forwarding prices, delivery time estimates), which is strong when-to-use guidance. It doesn't explicitly exclude alternatives, though the note that prices exclude import duties implicitly signals that landed-cost questions belong elsewhere.

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.