PackZoo
Server Details
Compare parcel and letter delivery prices across 60+ carriers in 27 European countries.
- 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 3.2/5 across 1 of 1 tools scored.
Only one tool exists, so there is no risk of confusing it with others.
The single tool name follows a clear verb_noun pattern and is well-formed.
With only one tool, the server feels thin for a shipping-related service, but it is not entirely trivial.
The server lacks supporting tools like carrier listing or package creation, which agents would likely need for a full shipping workflow.
Available Tools
2 toolscompare_shipping_pricesBInspect
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.
| 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. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention return format, sorting, error handling, caching, or any limitations like supported origin countries. The description is too sparse for a tool that likely queries external carrier APIs.
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 concise, using a single sentence that captures the core function without any filler, redundant, or unnecessary information.
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 6 required parameters, no output schema, and no annotations, the description lacks critical context. It does not explain the output format (e.g., list of prices with carrier names), whether it compares all carriers or a subset, or any assumptions about package dimensions. The description barely meets minimal viability.
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?
All 6 parameters are fully described in the input schema with clear descriptions (100% coverage). The tool description adds no additional semantic meaning beyond the schema, so a baseline score of 3 is appropriate.
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's function: comparing shipping prices across carriers. The verb 'compare' and resource 'shipping prices' are specific, and the description inherently distinguishes it from single-carrier lookup tools, even though no sibling tools are listed.
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?
The description provides no guidance on when to use this tool versus alternatives, such as for finding the cheapest option or for specific carriers. It also does not mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_carriersInspect
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.
| 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. |
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!