Skip to main content
Glama

Track a package (DHL, FedEx, UPS, USPS tracking link)

track_shipment
Read-onlyIdempotent

Returns the official carrier tracking URL for a DHL, FedEx, UPS or USPS tracking number (carrier auto-detected from the number format if not given). GS ships with these carriers and emails the tracking number on dispatch.

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_shipment"
  }
}

Input Schema

NameRequiredDescriptionDefault
carrierNo
tracking_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the burden is lighter. The description still adds valuable behavior beyond them: the return value is a constructed URL, not live tracking status, and it explains where a tracking number comes from ('emails the tracking number on dispatch'), which prevents an agent from expecting status updates.

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 sentences, front-loaded with the return value and carrier scope, with the operational aside about dispatch emails last. No redundant restatement of the name or title.

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?

A two-parameter read tool with no output schema needs little, and the description covers inputs, the auto-detection fallback, and what is returned. The only real omission is behavior for unsupported or unrecognized carrier formats.

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 0%, so the description must carry the load; it does explain the key semantic that carrier is optional and auto-detected from the number format when omitted. It does not explain the 6-40 character constraint or what happens with an unrecognizable number format, leaving a partial gap.

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 and resource ('Returns the official carrier tracking URL') plus the exact carrier set covered, which cleanly separates it from quote, rate, and landed-cost siblings. An agent can tell from the first clause that this resolves a tracking number to a URL rather than fetching live status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description indicates this is the tool for a tracking number and that the carrier can be omitted, but it never states when to prefer it or when it is inappropriate (e.g., for carriers outside the four listed). No alternative is named, though the siblings are quote/rate tools rather than tracking alternatives.

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.