Skip to main content
Glama
SuxyEE
by SuxyEE

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SLS_NETWORKNo网络类型:public(默认,公网)或 vpc(VPC 内网,适合服务器部署) (Network type: public or vpc)public
SLS_REGIONSNo地域配置,多个用英文逗号分隔,单个直接填写即可。如 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_IDYes阿里云 AccessKey ID (Alibaba Cloud AccessKey ID)
ALIBABA_CLOUD_ACCESS_KEY_SECRETYes阿里云 AccessKey Secret (Alibaba Cloud AccessKey Secret)

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_projectsA

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_logstoresA

List all logstores within an SLS project. Use this to discover available logstores before querying logs.

query_logsA

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_sqlA

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_histogramA

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_logsA

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: list_projects and list_logstores are for discovery, query_logs and query_logs_sql are for different query methods, get_log_histogram provides time-series analysis, and get_context_logs offers contextual retrieval. The descriptions explicitly differentiate their use cases, eliminating any ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_projects, query_logs, get_log_histogram). The naming is predictable and readable throughout, making it easy for agents to understand the action and target resource without confusion.

Tool Count5/5

With 6 tools, the server is well-scoped for log analysis and management in Aliyun SLS. Each tool earns its place by covering essential operations like discovery, querying, aggregation, and contextual analysis, without being overly sparse or bloated for the domain.

Completeness4/5

The toolset provides strong coverage for core log analysis workflows, including discovery, querying, aggregation, and contextual retrieval. A minor gap exists in lacking explicit CRUD operations for managing logstores or projects (e.g., create/delete), but this is reasonable for a read-focused analysis server, and agents can still perform most tasks effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues