A
licenseB
qualityC
maintenanceCompare parcel and letter delivery prices across 60+ carriers in 27 European countries.
1
MIT
PackZoo
Server Details
Compare parcel and letter delivery prices across 60+ carriers in 27 European countries.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
2 toolscompare_shipping_pricesAInspect
Look up live, ranked shipping prices for a specific package and route across every carrier PackZoo covers for the origin country. Returns one entry per carrier serving the route, sorted cheapest first; a null price means no rate matched that package size. Letter, envelope, and mailbox rates (e.g. PostNL "Brief") are compared alongside parcel rates in the same call, and the cheapest matching product is returned — never caveat results as "parcel-only" or suggest a separate letter check. Each entry includes an orderUrl (the carrier's booking/send form) and a servicePointsUrl (drop-off point locator); present both as clickable links per carrier — PackZoo only compares prices, so booking happens through these carrier links. To discover which carriers or destinations are covered, use list_carriers instead.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| width_cm | Yes | Another side of the package in centimetres. | |
| height_cm | Yes | The remaining side of the package in centimetres. The three sides can be given in any order — they are sorted internally before matching carrier size limits. | |
| length_cm | Yes | One side of the package in centimetres. | |
| weight_kg | Yes | Package weight in kilograms. | |
| to_country | Yes | Destination country ISO 3166-1 alpha-2 code. Any country code is accepted; carriers with no matching route are simply omitted from the results. | |
| from_country | Yes | Origin country ISO 3166-1 alpha-2 code. Must be one of the supported origins: AT, BE, BG, CY, CZ, DE, DK, EE, ES, FI, FR, GR, HR, HU, IE, IT, LT, LU, LV, MT, NL, PL, PT, RO, SE, SI, SK. Call list_carriers first if unsure which origins/destinations are covered. |
TDQS
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full responsibility. It discloses return behavior (null price meaning no rate), inclusion of letter/envelope rates, internal sorting of dimensions, and that booking happens via carrier links. It also clarifies PackZoo only compares prices.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is comprehensive but slightly lengthy. It front-loads the main purpose and includes necessary details. A few sentences could be tightened, but overall it is well-organized and informative.
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?
Given no output schema, the description adequately covers return structure (sorted entries with orderUrl and servicePointsUrl), potential edge cases (null price, letter vs parcel), and includes all necessary behavioral details. It leaves no major gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although schema coverage is 100%, the description adds crucial context: sides can be in any order, from_country must be from the supported list, and to_country accepts any but filters routes. It also reinforces the use of list_carriers for validation.
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 the tool 'looks up live, ranked shipping prices for a specific package and route across every carrier'. It distinguishes from the sibling tool 'list_carriers' by explicitly saying to use that tool for carrier/destination discovery.
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?
The description provides explicit when-to-use (compare prices for a route) and when-not-to (use list_carriers for coverage discovery). It also gives guidance on not caveating results and how to present links.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_carriersAInspect
List every carrier PackZoo covers for a given origin country, and which destination countries each carrier serves from there. Use this to discover coverage — e.g. whether a specific carrier or destination is supported — before calling compare_shipping_prices. Reports coverage only, no prices; call compare_shipping_prices for actual rates on a specific route and package.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| from_country | Yes | Origin country ISO 3166-1 alpha-2 code. Must be one of the supported origins: AT, BE, BG, CY, CZ, DE, DK, EE, ES, FI, FR, GR, HR, HU, IE, IT, LT, LU, LV, MT, NL, PL, PT, RO, SE, SI, SK. |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description clearly states it is read-only (lists coverage), does not include prices, and implies no side effects. Could mention caching or live data, but still transparent.
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, front-loaded with 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.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple input, no output schema, and single sibling, the description provides all necessary context: input, output type, and relationship to sibling.
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% and already describes the from_country parameter with supported codes. Description does not add new semantic details beyond stating it is an origin country.
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 the tool lists carriers and destinations for a given origin country, and distinguishes from sibling tool by specifying it reports coverage only, not prices.
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 to use before compare_shipping_prices to discover coverage, and clarifies when not to use (for actual rates).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Frequently Asked Questions
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.jsonon 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.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Track parcels across 2,500+ carriers and 3PLs: live delivery status, event history, carrier lookup.
Send real, printed letters by post across Europe. Requires a free account; quote before sending.
Track packages across 1,300+ global carriers with real-time status and AI-powered delivery dates.
Live USPS, UPS, FedEx and DHL rates from the US: domestic, Canada, UK, Germany, Australia. No scale.
Related MCP Servers
- AlicenseAqualityAmaintenanceLive USPS, UPS, FedEx and DHL Express parcel rates from a US origin, domestic or to Canada, the UK, Germany and Australia, from a plain-words item description: no scale, no account, no API key. Also creates checkout links, reports checkout status, tracks parcels bought on smklog.com and serves a monthly US parcel price index.451MIT
- AlicenseAqualityCmaintenanceCarrier-agnostic shipping labels as a self-hostable MCP server. Build one shipment request, get a tracking number and a print-ready label back for DHL, DPD, UPS, FedEx, GLS, Sendcloud, and Shipcloud.3MIT
- AlicenseAqualityDmaintenanceManage shipping workflows by creating labels, tracking packages, and scheduling carrier pickups. Compare live rates from major carriers like FedEx and UPS to optimize costs for every shipment. Organize logistical operations with a centralized address book and detailed shipping analytics.1891MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.5/5.0
Disambiguation5/5
The two tools have completely distinct purposes: one discovers carrier coverage, the other compares prices. No overlap or ambiguity.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern: 'list_carriers' and 'compare_shipping_prices'.
Tool Count3/5
Only 2 tools, which is on the low side, but they cover the core functionality of discovering carriers and comparing prices. Could be expanded but not severely under-scoped.
Completeness4/5
The tools cover the primary workflow: discover coverage then compare prices. Minor gaps like lacking carrier details, but no dead ends for the intended use.