Skip to main content
Glama

easypost

by io.usefulapi

Create a shipment (get rates)

easypost_create_shipment

Create a shipment from a to_address, from_address, and parcel, returning the available RATES from all enabled carriers. This only RATES the shipment — it does NOT purchase a label and does NOT charge the account; buying is a separate step (easypost_buy_shipment). API: POST /shipments (body { shipment }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parcelYesPackage dimensions and weight.
referenceNoYour internal reference string for the shipment.
to_addressYesDestination address.
from_addressYesOrigin/return address.
carrier_accountsNoRestrict rating to these carrier_account ids.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate non-destructive (readOnlyHint=false, destructiveHint=false). Description adds confirmation by stating no purchase/charge, and mentions the API endpoint. No contradictions.

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, no filler. Front-loaded with purpose, followed by critical usage constraint. Each sentence adds value.

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?

Tool has 5 params fully documented in schema; no output schema but description says returns rates. Includes API endpoint for reference. Complete for this complexity level.

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%, so the schema documents all parameters. The description adds little beyond listing the three main objects; baseline 3 is appropriate.

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 states 'Create a shipment... returning the available RATES from all enabled carriers' and emphasizes it only rates, not purchases, clearly distinguishing from easypost_buy_shipment.

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

Usage Guidelines5/5

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

Explicitly says 'This only RATES the shipment — it does NOT purchase a label... buying is a separate step (easypost_buy_shipment)', providing clear when and when-not to use.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose: address operations, shipment lifecycle (create, buy, refund, get, list), and tracking. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent `easypost_<verb>_<resource>` pattern using snake_case, with clear verbs like create, get, list, buy, refund, verify.

Tool Count5/5

11 tools cover the essential operations for address management, shipment lifecycle, and tracking without being too many or too few.

Completeness4/5

Core workflows (rate, buy, refund, track, address verification) are complete. Minor gaps like missing delete for addresses or update for shipments are acceptable for the domain.

Resources