aliyun-sls-codex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALIBABA_CLOUD_ACCESS_KEY_ID | Yes | Your Alibaba Cloud Access Key ID for read-only SLS access. | |
| ALIBABA_CLOUD_ACCESS_KEY_SECRET | Yes | Your Alibaba Cloud Access Key Secret for read-only SLS access. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logsA | Search application logs by one or more content keywords. |
| get_context_logsC | Get logs around an anchor Unix timestamp. |
| check_connectionA | Check read-only SLS connectivity. |
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 3 tools
Each tool has a clear, distinct purpose: search by keywords, fetch context around a timestamp, and verify connectivity. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: search_logs, get_context_logs, check_connection. The naming is uniform and predictable.
With 3 tools, the server is well-scoped for a focused log-searching utility. Each tool is essential to the core workflow of finding and examining logs.
The tools cover the main workflow of searching logs and retrieving surrounding context, but lack explicit time-range controls or the ability to list available log stores. These are minor gaps that can be worked around with existing parameters or configuration.