DB Schenker Shipment Information MCP Server
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_shipment_infoA | Retrieves live tracking data of a DB Schenker shipment. Args: reference_number: DB Schenker Reference number for the shipment Returns: A dictionary containing shipment information and error messages if there are any. |
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 risk of confusion between tools. The single tool's purpose is clearly distinct by default.
A single tool named 'get_shipment_info' follows a clear verb_noun pattern. Consistency is not an issue.
The server has only one tool, which feels thin for a shipment tracking service. Additional tools like list_shipments or track_multiple would be expected for broader utility.
The tool surface is severely incomplete. It only supports retrieval by a single reference number, missing essential operations such as listing shipments, error handling for invalid references, or batch queries.