AirboxShip Shipping (public)

Track a Package

track_package

Read-onlyIdempotent

Look up the current status of a USPS package by its tracking number.

Returns the status, USPS's one-line summary, the expected delivery date and the latest scan
(what happened, when, and the city and state). The same information usps.com shows anyone who
has the number. USPS packages only: a UPS number gets an error pointing to ups.com.

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": {
      "tracking_number": "<tracking_number>"
    },
    "name": "track_package"
  }
}

Input Schema

Name	Required	Description	Default
`tracking_number`	Yes	USPS tracking number, e.g. '9400111899223197428490'

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, and the description still adds real substance: the exact fields returned (status, one-line summary, expected delivery date, latest scan with time and location), the fact that no authentication or account is needed ('the same information usps.com shows anyone who has the number'), and the failure mode for non-USPS numbers.

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?

Four short sentences, front-loaded with the purpose, then returns, then the scope caveat. The 'same information usps.com shows' line is slightly indirect but earns its place by conveying the public/no-auth nature of the data.

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 carries the burden of explaining return values, and it does so concretely. For a single-parameter, read-only lookup, nothing an agent needs in order to call it or interpret the result is missing.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter already has an example, so the baseline is 3. The description earns above baseline by constraining the value domain: the number must be a USPS tracking number, and a UPS number will error rather than silently return nothing.

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 opens with a specific verb and resource: 'Look up the current status of a USPS package by its tracking number.' That is instantly distinguishable from the sibling tools find_pickup_hubs and get_shipping_rates, which concern locations and pricing rather than shipment status.

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 a clear condition for use (you have a tracking number and want current status) and a boundary case: 'USPS packages only: a UPS number gets an error pointing to ups.com.' It does not explicitly say when to prefer this over get_shipping_rates, but the domains are far enough apart that this is a minor gap.

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

All AirboxShip Shipping (public) tools Inspect

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

Need Help?