mcp-logistics-tracker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAGAWA_API_KEY | No | Direct Sagawa API key (not implemented - leads to error if set alone) | |
| YAMATO_API_KEY | No | Direct Yamato API key (not implemented - leads to error if set alone) | |
| AFTERSHIP_API_KEY | No | AfterShip API key for real tracking connection (optional; if not set, mock mode is used) | |
| JAPANPOST_API_KEY | No | Direct Japan Post API key (not implemented - leads to error if set alone) |
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 |
|---|---|
| list_carriersA | 対応している配送業者（ヤマト運輸・佐川急便・日本郵便）の一覧を返す。 |
| track_shipmentA | 指定した配送業者・追跡番号の現在の配送状況（最新ステータス）を返す。 Args: carrier: 配送業者コード（例: yamato / sagawa / japanpost）。 tracking_number: 追跡番号（数字。ハイフン/空白は自動除去）。 |
| get_tracking_historyA | 指定した配送業者・追跡番号の配送イベント履歴を時系列で返す。 Args: carrier: 配送業者コード（例: yamato / sagawa / japanpost）。 tracking_number: 追跡番号（数字。ハイフン/空白は自動除去）。 |
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 3 tools
Each tool has a clearly distinct purpose: listing carriers, fetching current status, and retrieving full history. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (get_tracking_history, list_carriers, track_shipment), making them predictable and readable.
With 3 tools covering listing carriers, current status, and history, the number is well-scoped for a basic logistics tracking server. Each tool earns its place.
The tool surface covers the core tracking workflow (carrier discovery, current status, full history). While additional features like batch tracking or validation could be useful, there are no critical gaps.