Aliyun 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| querySLSLogsC | Query Aliyun SLS (Simple Log Service) logs |
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 querying Aliyun SLS logs, making it distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'querySLSLogs' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'Aliyun MCP Server', which implies broader cloud service functionality. This minimal toolset severely limits the server's scope and utility, making it feel incomplete and underpowered for its apparent purpose.
The server appears to target Aliyun cloud services, but with only a log querying tool, there are significant gaps in coverage. Missing are core operations like managing resources (e.g., creating/deleting instances), monitoring, or other SLS functions beyond querying, making the surface severely incomplete.