mcp-scalyr-dataset
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATASET_BASE_URL | Yes | Operator-set HTTPS region base URL, e.g. https://app.scalyr.com (US) or https://app.eu.scalyr.com (EU). | |
| DATASET_READ_TOKEN | Yes | Log Read Access Bearer token. The only required key / scope — Config Read and Write are never required. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_logsA | Return a small page of matching DataSet/Scalyr log events as a compact fenced pipe table. Prefer count_logs or list_log_facets first, then a tight filter. One page per call; use continuation_token for the next page (never auto-paginated). |
| count_logsA | Volume check before search_logs. Returns count/filter/window/cpu_ms only — no event bodies. |
| list_log_facetsA | Top values for one field (hosts, files, severity). Use before narrowing search_logs filters. |
| power_queryA | Run a DataSet PowerQuery (group, sort, count, filter, let, join, timebucket). Not for dumping raw messages — use search_logs for that. | columns alone is rejected. |
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 4 tools
The four tools map to reasonably distinct jobs: facet discovery, volume counting, raw event retrieval, and aggregation. There is mild overlap — count_logs and power_query can both produce counts, and power_query can filter the same data search_logs filters — but the descriptions explicitly steer callers (e.g. 'not for dumping raw messages — use search_logs').
Three of four names follow a clean verb_noun pattern (search_logs, count_logs, list_log_facets) with a shared 'logs'/'facet' vocabulary. power_query deviates by naming a product feature rather than an action, but it is still readable and unambiguous.
Four tools is a lean but defensible surface for a log-query server covering discovery, counting, search, and aggregation. It sits slightly on the thin side — there is no schema/field-listing tool to support exploration — but no tool feels redundant.
Search, count, facet discovery, and aggregation with a continuation_token cover the core query workflow. However, list_log_facets requires already knowing a field name, and there is no way to enumerate fields/datasets or to fetch a specific event or surrounding context, which will cause dead ends for an agent exploring an unfamiliar dataset.