Skip to main content
Glama

AirboxShip Shipping (public)

Get Shipping Rates

get_shipping_rates
Read-onlyIdempotent

Get shipping rates (postage cost and delivery time) for mailing a package with USPS or UPS home delivery, between two US addresses.

Returns each option's carrier, service, price in USD and estimated delivery time at the standard price. Quotes are indicative and not reserved. This tool only quotes prices; it does not buy a label.

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": {
      "sender_name": "<sender_name>",
      "sender_street1": "<sender_street1>",
      "sender_city": "<sender_city>",
      "sender_state": "<sender_state>",
      "sender_zip": "<sender_zip>",
      "recipient_name": "<recipient_name>",
      "recipient_street1": "<recipient_street1>",
      "recipient_city": "<recipient_city>",
      "recipient_state": "<recipient_state>",
      "recipient_zip": "<recipient_zip>",
      "weight_lb": "<weight_lb>",
      "length_in": "<length_in>",
      "width_in": "<width_in>",
      "height_in": "<height_in>"
    },
    "name": "get_shipping_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
width_inYesPackage width in inches
height_inYesPackage height in inches
length_inYesPackage length in inches
weight_lbYesPackage weight in pounds, e.g. 2.5
sender_zipYesUS ZIP code, e.g. '94103'
sender_cityYesCity name, e.g. 'San Francisco'
sender_nameYesFull name of the person or business at this address
sender_stateYesTwo-letter US state code, e.g. 'CA'
recipient_zipYesUS ZIP code, e.g. '94103'
recipient_cityYesCity name, e.g. 'San Francisco'
recipient_nameYesFull name of the person or business at this address
sender_street1YesStreet address line, e.g. '123 Main St'
recipient_stateYesTwo-letter US state code, e.g. 'CA'
recipient_street1YesStreet address line, e.g. '123 Main St'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 behavior, so the bar is lower. The description still adds real value beyond them: quotes are 'indicative and not reserved' and priced at the 'standard price', which an agent needs to know before presenting costs as bookable. It does not mention rate limits or failure behavior for invalid addresses.

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 short sentences: the capability and scope first, then what is returned and the non-purchase caveat. Nothing is repeated from the schema and no sentence is filler.

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?

There is no output schema, so the description appropriately enumerates the returned fields and clarifies that prices are indicative and unpurchased. Combined with fully documented required parameters and safety annotations, an agent has everything needed to call it and interpret the result.

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%, with every one of the 14 required fields documented with examples, so the schema carries parameter meaning. The description contributes only the constraint that both addresses must be US; it adds no guidance on how weight and dimensions affect quotes. Baseline 3 applies.

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 (get shipping rates), the carriers covered (USPS, UPS home delivery), the route type (between two US addresses), and exactly what the response contains (carrier, service, USD price, delivery time). That is far more than a restatement of the title and lets an agent distinguish this from tracking or pickup-hub lookups.

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 clearly states the operation's boundary — 'This tool only quotes prices; it does not buy a label' — which tells the agent when not to use it. It stops short of naming what to call instead for label purchase or tracking, so it is strong context without full routing guidance.

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.

Resources