Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SLS_NETWORK | No | 网络类型：public（默认，公网）或 vpc（VPC 内网，适合服务器部署） (Network type: public or vpc) | public |
| SLS_REGIONS | No | 地域配置，多个用英文逗号分隔，单个直接填写即可。如 cn-hangzhou 或 cn-hangzhou,cn-shenzhen,cn-beijing。不填默认使用 cn-hangzhou (Region configuration, multiple regions separated by commas, e.g., cn-hangzhou,cn-shenzhen) | cn-hangzhou |
| ALIBABA_CLOUD_ACCESS_KEY_ID | Yes | 阿里云 AccessKey ID (Alibaba Cloud AccessKey ID) | |
| ALIBABA_CLOUD_ACCESS_KEY_SECRET | Yes | 阿里云 AccessKey Secret (Alibaba Cloud AccessKey Secret) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projects | List all SLS projects in one or more Alibaba Cloud regions. Pass a single region string or an array of region IDs. If omitted, queries all regions configured in SLS_REGIONS / SLS_REGION env variables. Use this to discover available projects before querying logs. |
| list_logstores | List all logstores within an SLS project. Use this to discover available logstores before querying logs. |
| query_logs | Query log data from an SLS logstore with a time range and optional filter query. Returns formatted log entries. Use for debugging, error investigation, and log analysis. Supports SLS query syntax like "level: ERROR", "content: timeout", "status: 500 AND method: POST". |
| query_logs_sql | Execute a SQL query against an SLS project for log analysis and aggregation. Best for counting, grouping, statistical analysis. Example: "SELECT status, count(*) as cnt FROM WHERE time > 1700000000 GROUP BY status". |
| get_log_histogram | Get the time-series distribution of log counts matching a query. Returns a visual histogram showing log volume over time. Useful for identifying when errors spiked or when unusual activity occurred. |
| get_context_logs | Retrieve log lines before and after a specific log entry using its pack_id and pack_meta. First query logs with query_logs to find a log entry, then use its tag:pack_id and tag:pack_meta fields to get surrounding context. Useful for understanding full execution flow around an error. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |