DB Schenker Shipment Tracker
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 |
|---|---|
| track_shipmentA | Track a DB Schenker shipment by reference number and return structured shipment details and tracking history. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as tracking shipments, leaving no room for misselection.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'track_shipment' follows a clear verb_noun pattern.
A single tool is too few for a shipment tracking server, as it lacks basic operations like listing shipments, creating shipments, or updating shipment details. This minimal scope will likely cause agent failures in handling complex workflows.
The tool set is severely incomplete for a shipment tracking domain. It only provides tracking functionality, missing essential operations such as creating shipments, managing shipment statuses, or retrieving shipment lists, which are critical for full coverage.