PackZoo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_shipping_pricesB | Compare shipping prices across carriers for a given package and route. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is clear and distinct.
The tool name 'compare_shipping_prices' follows a clear verb_noun pattern, which is consistent and descriptive. There are no other tools to conflict.
With only one tool, the server feels overly minimal. While a focused price comparison service could justify a single tool, users typically expect additional related operations (e.g., carrier list, package validation) making this count too low for practical use.
The server only offers a single price comparison operation. It lacks supporting tools for managing carriers, packages, or viewing historical data, leaving significant gaps for any realistic shipping workflow.