parcel-quotes
Server Details
Live USPS, UPS and FedEx rates for a US parcel described in plain words. No scale needed.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: one for getting a parcel quote and one for creating a checkout link. There is no functional overlap; they represent sequential steps in a workflow.
Both tool names follow a consistent verb_noun pattern in snake_case: 'get_parcel_quote' and 'create_checkout_link'. No stylistic inconsistencies.
With only 2 tools, the server is minimally scoped but covers the essential operations for its purpose (quoting and initiating checkout). It is slightly thin but still reasonable for a focused integration.
The tool surface covers the core workflow: obtaining a quote and creating a checkout link to complete the purchase on the external site. No obvious gaps for the stated purpose of parcel quotes and checkout initiation.
Available Tools
2 toolscreate_checkout_linkCreate a payment session for a parcel labelAInspect
Prices the shipment live and returns a payment session: the amount, and a handoff URL that opens the SMKlog checkout prefilled with this shipment. The human confirms the contents certification and the carrier-adjustment consent there and pays on Stripe hosted checkout. This tool never charges anything itself — MPP intent "session", not "charge".
| Name | Required | Description | Default |
|---|---|---|---|
| to_zip | Yes | Destination 5-digit US ZIP | |
| product | Yes | Plain-words item description | |
| service | No | Optional service to anchor the amount, e.g. "USPS Ground Advantage". Cheapest when omitted; the human can still pick any service on the page. | |
| from_zip | Yes | Origin 5-digit US ZIP | |
| quantity | No |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that the tool never charges itself (intent is session, not charge) and explains the human confirmation and payment flow. Lacks details on side effects like session creation or idempotency, but good overall.
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?
Three sentences, front-loaded with main purpose, no redundant information. Every sentence adds value.
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?
Explains return value (amount and handoff URL) and user interaction. Given no output schema, covers main behavior well, though error conditions are omitted.
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?
With 80% schema coverage, description adds value: explains 'service' as optional with cheapest default and that human can choose any service, and 'product' as plain-words description. Goes beyond 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?
Clearly states it creates a payment session for a parcel label, explaining the live pricing and handoff URL. Distinguishes from get_parcel_quote by specifying it returns a payment session handoff, not just a quote.
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 context that this tool is used for the payment step, but does not explicitly state when to use over alternatives or prerequisites like needing a quote first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_parcel_quoteGet live US parcel shipping ratesAInspect
Price one US-domestic parcel across USPS, UPS and FedEx. Describe the item in plain words and the packed box size and weight are estimated; give exact dimensions and weight to skip the estimate. Returns up to five purchasable services with the checkout total, the carrier cost beneath it and the SMKlog fee stated separately. Oversized, palletized or crated shipments come back routed to a human review instead of a price. Labels are bought on smklog.com, not through this tool.
| Name | Required | Description | Default |
|---|---|---|---|
| to_zip | Yes | Destination 5-digit US ZIP | |
| product | Yes | Plain-words item description, e.g. "65 inch flat screen TV in original box" | |
| from_zip | Yes | Origin 5-digit US ZIP | |
| quantity | No | ||
| width_in | No | ||
| height_in | No | ||
| length_in | No | Packed box length in inches. Supply all three dimensions AND weight_lb to skip the estimate. | |
| weight_lb | No | Packed weight in pounds. Optional; estimated from the description when omitted. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description carries full burden. It discloses estimation behavior, return format (up to five purchasable services with checkout total, carrier cost, SMKlog fee), and routing of oversized shipments to human review. Fully transparent.
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?
Three sentences, front-loaded with main action, no redundant information. Every sentence adds value.
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?
With 8 parameters, no output schema, and no annotations, the description covers input behavior (estimation, exact dimensions), output structure, and edge cases (oversized items). Very complete for the complexity.
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 63%, but description adds meaning: explains that 'product' should be in plain words, that dimension parameters are optional but skip estimation, and that 'weight_lb' is optional. Adds context beyond 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 prices a US-domestic parcel across USPS, UPS, and FedEx, which is a specific verb+resource combination. It distinguishes from the sibling tool 'create_checkout_link' which is for purchasing labels.
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 guidance: describe item in plain words, supply exact dimensions to skip estimate, notes oversized items go to human review, and clarifies labels are bought elsewhere. Does not explicitly contrast with sibling, but context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!