Skip to main content
Glama

PackZoo

by io.github.IAfanasov

list_carriers

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_countryYesOrigin 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.

All PackZoo 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.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.

Resources