Skip to main content
Glama
mcp-scalyr-dataset

mcp-scalyr-dataset

by RexySaragih

power_query

Read-onlyIdempotent

Run DataSet PowerQuery aggregations—group, sort, count, filter, let, join, and timebucket—to summarize log events; use search_logs instead when dumping raw messages.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "power_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPowerQuery with a pipe stage (| group, | sort, | count(, | filter, | let, | join, or | timebucket). | columns alone is rejected.
end_timeNo
priorityNo
start_timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety behavior is covered structurally. The description adds one useful behavioral constraint — that a '| columns' stage alone is rejected — but says nothing about result shape, size limits, or whether the query is scoped by the time parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the capability list followed by the exclusion, with no filler. The 'columns alone is rejected' clause is repeated from the query parameter description, which is minor redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter query-language tool with no output schema, the description covers what the query language accepts and what to avoid, but leaves the time-window parameters and priority filter unexplained and does not describe the returned records. An agent would need to guess how start_time/end_time interact with the query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%: query has a description, while start_time, end_time and priority have none. The description only reiterates the pipe-stage requirement for query (already in the schema) and does not compensate for the undocumented time-range and priority parameters, whose meaning and interaction with the query must be inferred.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb and resource ('Run a DataSet PowerQuery') and enumerates the supported operations (group, sort, count, filter, let, join, timebucket). It also contrasts itself with search_logs, so an agent can distinguish it from siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states the anti-pattern ('Not for dumping raw messages') and names the alternative tool, search_logs, that handles that case. It gives no guidance on when to prefer count_logs or list_log_facets, but the primary exclusion is stated clearly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools