Skip to main content
Glama
Sign In

Easypost

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Easypost Rates

easypost_rates
Read-onlyIdempotent

Get shipping rate quotes from <from_zip> to <to_zip> for a parcel — returns multi-carrier rates (USPS, UPS, FedEx, etc.) with price, service level, and estimated delivery days. Example: easypost_rates({ from_zip: "94105", to_zip: "10001", weight_oz: 16, _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": {
      "to_zip": "10001",
      "_apiKey": "your-easypost-api-key",
      "from_zip": "94105",
      "weight_oz": 16
    },
    "name": "easypost_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_zipYesDestination postal/ZIP code, e.g. "10001"
_apiKeyYesEasyPost API key (get one free at easypost.com)
to_cityNoDestination city (optional), e.g. "New York"
from_zipYesOrigin postal/ZIP code, e.g. "94105"
to_stateNoDestination state/province code (optional), e.g. "NY"
width_inNoParcel width in inches (optional)
height_inNoParcel height in inches (optional)
length_inNoParcel length in inches (optional)
weight_ozYesParcel weight in ounces, e.g. 16 for 1 lb
to_countryNoDestination ISO country code (default "US")
from_countryNoOrigin ISO country code (default "US")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-easypost-api-key",
+    "from_zip": "94105",
+    "to_zip": "10001",
+    "weight_oz": 16
+  },
+  {
+    "_apiKey": "your-easypost-api-key",
+    "from_zip": "90210",
+    "height_in": 6,
+    "length_in": 12,
+    "to_city": "Chicago",
+    "to_state": "IL",
+    "to_zip": "60611",
+    "weight_oz": 32,
+    "width_in": 8
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds an example but does not disclose additional behavioral traits like API key authentication or rate limits beyond what the schema provides. No contradiction with annotations.

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: one explains functionality, one provides example. No wasted words, front-loaded with purpose. Perfectly concise for the complexity.

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?

Parameters fully documented in schema, description explains output (multi-carrier rates with price, service, delivery days). Lacks explanation of error cases (e.g., invalid zip) but this is acceptable given low tool complexity and rich schema.

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% with clear parameter descriptions. The description adds value by providing a concrete usage example showing how parameters combine (e.g., from_zip, to_zip, weight_oz, _apiKey), which aids understanding beyond the schema alone.

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 clearly states it 'Get shipping rate quotes' with specific source/destination and parcel, and lists return fields (multi-carrier rates, price, service level, delivery days). This distinguishes it from sibling easypost_track (tracking) and provides a concrete verb+resource.

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 implies usage for rate quotes but does not explicitly state when to use over alternatives like easypost_track. No 'when-not' or prerequisite guidance is provided; the context is implicit via the example.

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