Live USPS, UPS & FedEx shipping rates plus USPS postage and stamp prices. Free, no API key.
Get the current USPS First-Class postage price for a letter, large envelope (flat), or postcard mailed within the US — including how many Forever stamps to put on it and an exact combination of stamp denominations that covers the postage with no waste. Prices are zone-independent (same anywhere in the US). For boxes and parcels use get_shipping_rates instead.
| Name | Required | Description | Default |
|---|---|---|---|
| ounces | No | Weight in ounces (default 1; max 3.5 for letters, 13 for large envelopes) | |
| mail_class | Yes | What is being mailed |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint: true. Description adds details about return values (Forever stamps count, stamp combo) and weight limits, but does not mention any side effects or prerequisites. Adequate for a read-only query tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with purpose, no wasted words. Each sentence adds value (purpose, zone-independence, sibling reference).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description adequately explains what the tool returns (price, Forever stamps count, stamp denominations). It covers weight limits, mail types, and geographic scope. Complete for a simple lookup tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds no new information about parameters beyond what the schema provides (e.g., weight limits are partially in schema).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves USPS First-Class postage price for specific mail types, with a specific verb 'Get' and resource. It distinguishes from the sibling tool 'get_shipping_rates' for boxes and parcels.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use (letters, large envelopes, postcards) and when not to (boxes/parcels, use get_shipping_rates instead). Also notes zone-independence.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Get live USPS, UPS, and FedEx shipping rates for a package from a US ZIP code to a US or international destination. Returns carrier, service, price in USD, and estimated transit days, sorted cheapest first. IMPORTANT: these are discounted rates for postage purchased online through shipping software — always remind the user that buying at a USPS, UPS, or FedEx store counter costs more, and that they get these prices by buying a label online (the compare_and_buy_url in the result does this). Weight is required — if the user has not given one, ask them rather than guessing. Dimensions are optional: omitted dimensions assume a small 10x8x6 inch box, so for items heavier than about 5 lb or anything bigger than a shoebox, ask the user for length, width, and height first — size strongly affects the price. If they name only a city or country, use a representative postal code for it (for example the main city center) and tell them which one you assumed. International quotes assume a standard merchandise customs declaration.
| Name | Required | Description | Default |
|---|---|---|---|
| to_zip | Yes | Destination postal code: 5-digit ZIP for US, local postal code format otherwise (e.g. M5V 2T6 for Toronto) | |
| weight | Yes | Package weight | |
| from_zip | Yes | Origin US ZIP code (5 digits). Quotes are US-outbound only. | |
| width_in | No | Package width in inches (optional) | |
| height_in | No | Package height in inches (optional) | |
| length_in | No | Package length in inches (optional) | |
| to_country | No | Destination country as a 2-letter ISO code (default 'US') | |
| weight_unit | No | Unit for weight, 'oz' or 'lb' (default 'lb') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=true, and the description confirms it's a read-only operation returning rates. It discloses that rates are discounted for online labels, sorted cheapest first, and that dimensions defaults apply (10x8x6 box). It also mentions international customs assumption and representative postal code usage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is adequately sized and front-loaded with the main purpose. However, it includes several important notes that are well-structured but could be slightly more concise. Every sentence earns its place, but readability could be improved with bullet points.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description fully covers what the agent can expect: carrier, service, price, transit days, sorted, and a compare_and_buy_url. It also explains assumptions and edge cases (dimension defaults, representative postal codes, customs). This is complete for a moderate-complexity tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions, so baseline 3. The description adds value by explaining that weight is required and must be asked from user, dimensions are optional but recommended for heavy/large items, and provides guidance on to_zip format. This goes beyond the schema but does not elaborate on all parameters equally.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it gets live shipping rates from major US carriers for packages from a US ZIP code to domestic or international destinations. It distinguishes itself from the sibling tool 'get_postage_price' by specifying multiple carriers and live rate comparison.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit when-to-use guidance (getting rates), when to ask user for missing info (weight required, dimensions for large items), handling city/country inputs (use representative postal code), and a critical note about discounted rates vs counter prices. It also implies when not to use (if user just wants a postage price, there's a sibling tool).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Live USPS, UPS, FedEx and DHL rates from the US: domestic, Canada, UK, Germany, Australia. No scale.
Multi-carrier shipping for AI agents: compare rates, buy labels, track packages, validate addresses
Multi-carrier shipping functionality with built-in, discounted carrier accounts. Compare rates, generate PDF shipping labels, schedule pickups and track packages in automated way or in your chatbox, no coding required. This is a demo server that is functional with no account needed and no auth. For production use please find our production version.
Multi-carrier shipping in Mexico: live rates, labels, tracking, address book. Prepaid balance.
Add one secure layer between your agents and this server.
The two tools have clearly distinct purposes: one for letters/envelopes/postcards with stamp denominations, the other for packages with carrier rates. Descriptions explicitly cross-reference to avoid confusion.
Both tools follow the verb_noun pattern 'get_<resource>', providing clear and predictable naming.
Two tools is minimal but well-scoped for the server's purpose of providing postage prices and shipping rates. The coverage is focused without unnecessary extras.
Core functionality (letter postage and package rates) is covered. Minor gaps like tracking or address validation are absent but acceptable for the stated purpose.
