mcp-yuntrack
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 |
|---|---|
| track_parcelA | Track one or more parcels via YunTrack. Returns the raw JSON from the YunTrack Query API. |
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 ambiguity between tools. The tool's purpose is clearly defined as tracking parcels via YunTrack.
The single tool 'track_parcel' follows a clear verb_noun pattern using snake_case, which is consistent within itself.
One tool is quite thin for a typical MCP server, but it may be appropriate if the server is narrowly scoped to parcel tracking only. The tool handles multiple parcels in one call, reducing the need for additional tools.
For a simple parcel tracking server, the single tool covers the core functionality. Minor gaps might exist, such as listing carriers or getting tracking history, but these are not essential for basic tracking.