Skip to main content
Glama
Sign In

Easypost

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Easypost Track

easypost_track
Read-onlyIdempotent

Track a package by tracking number — returns current status, carrier, estimated delivery date, and recent scan events. Example: easypost_track({ tracking_code: "9400100000000000000000", carrier: "USPS", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-easypost-api-key",
      "carrier": "USPS",
      "tracking_code": "9400100000000000000000"
    },
    "name": "easypost_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesEasyPost API key (get one free at easypost.com)
carrierNoCarrier name (optional but recommended), e.g. "USPS", "UPS", "FedEx"
tracking_codeYesCarrier tracking number, e.g. "9400100000000000000000"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-easypost-api-key",
+    "carrier": "USPS",
+    "tracking_code": "9400100000000000000000"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds specific details about the return payload (current status, carrier, estimated delivery date, scan events), providing useful behavioral context beyond the annotations. No contradiction.

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 plus a short example. The first sentence states purpose and return fields. No filler, all content earns its place. Front-loaded with the most important information.

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?

For a read-only tracking tool with no output schema, the description covers what the tool returns (status, carrier, estimated delivery, scan events). Parameters are fully covered by schema. Could mention edge cases (e.g., invalid tracking code) but is sufficiently complete for common use.

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 coverage is 100% with each parameter having a description. The description adds an example call showing actual values and optionality of carrier. This is marginally helpful but does not significantly expand on the schema's documentation.

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 begins with a clear verb 'Track a package by tracking number' and specifies the resource (package) and input (tracking number). It lists return fields (status, carrier, estimated delivery date, recent scan events), distinguishing it from sibling 'easypost_rates' which handles rate lookups.

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?

The description provides an example call but no explicit guidance on when to use this tool versus alternatives (e.g., when needing tracking vs. rates). It does not state when not to use it or mention prerequisites beyond the API key.

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

All Easypost toolsInspect
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