ShippingTracker
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_company_listD | Get Company List |
| track_shippingC | Track Shipping with Company Code and Tracking Invoice |
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 2 tools
The two tools have clearly distinct purposes: get_company_list retrieves a list of companies, while track_shipping handles tracking shipments with specific identifiers. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun naming pattern (get_company_list, track_shipping) with clear, descriptive names. There are no deviations or mixed conventions.
With only 2 tools, the server feels thin for a 'ShippingTracker' domain. This minimal set likely lacks essential operations like creating shipments, updating tracking info, or managing companies, which are core to shipping workflows.
The tool surface is severely incomplete for a shipping tracking domain. It only provides retrieval (get_company_list) and tracking (track_shipping), missing critical operations such as creating shipments, updating statuses, deleting records, or handling returns, which will cause agent failures in real-world scenarios.