Alibaba Cloud Observability MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALIBABA_CLOUD_ACCESS_KEY_ID | No | Alibaba Cloud AccessKey ID for authentication | |
| ALIBABA_CLOUD_SECURITY_TOKEN | No | Alibaba Cloud Security Token for STS authentication | |
| ALIBABA_CLOUD_ACCESS_KEY_SECRET | No | Alibaba Cloud AccessKey Secret for authentication |
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 |
|---|---|
| sls_list_projectsA | 列出阿里云日志服务中的所有项目。 |
| sls_list_logstoresA | 列出SLS项目中的日志库。 |
| sls_describe_logstoreA | 获取SLS日志库的结构信息。 |
| sls_execute_queryB | 执行SLS日志查询。 |
| sls_translate_natural_language_to_queryA | 将自然语言转换为SLS查询语句。 |
| sls_diagnose_queryA | 诊断SLS查询语句。 |
| sls_get_current_timeA | 获取当前时间信息。 |
| arms_search_appsA | 搜索ARMS应用。 |
| arms_generate_trace_queryA | 生成ARMS应用的调用链查询语句。 |
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 9 tools
Each tool has a clearly distinct purpose with no overlap. The tools are organized into two main categories: ARMS application monitoring tools (arms_generate_trace_query, arms_search_apps) and SLS log service tools (the remaining seven), with each addressing specific operations like query generation, search, description, diagnosis, execution, time retrieval, listing, and translation. The descriptions clearly differentiate their functions, preventing misselection.
Tool names follow a highly consistent pattern throughout. All names use snake_case and a clear prefix-action-resource structure (e.g., arms_search_apps, sls_execute_query). The prefixes 'arms_' and 'sls_' denote the service domain, followed by a verb (e.g., generate, search, describe, diagnose) and a noun (e.g., trace_query, apps, logstore), making the set predictable and readable.
With 9 tools, the count is well-scoped for an observability server covering ARMS and SLS services. Each tool earns its place by addressing core operations like listing resources, executing queries, generating queries from natural language, and diagnosing issues. This provides comprehensive coverage without being overwhelming or too sparse for the domain.
The tool set offers complete coverage for the observability domain, including CRUD-like operations for logs and traces. It supports listing projects and logstores, describing structures, executing and diagnosing queries, translating natural language, and managing ARMS applications. There are no obvious gaps; tools like sls_get_current_time and sls_diagnose_query add utility for time handling and error analysis, ensuring agents can handle full workflows without dead ends.