Skip to main content
Glama
mcp-scalyr-dataset

mcp-scalyr-dataset

by RexySaragih

count_logs

Read-onlyIdempotent

Checks log volume before searching by returning counts for a required DataSet filter, with optional time window and priority, and no event bodies.

Instructions

Volume check before search_logs. Returns count/filter/window/cpu_ms only — no event bodies.

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": {
      "filter": "<filter>"
    },
    "name": "count_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterYesDataSet filter (required non-empty)
end_timeNo
priorityNo
start_timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety bar is low. The description adds real value beyond them by enumerating the return payload (count/filter/window/cpu_ms) and explicitly stating no event bodies are returned, plus cpu_ms signals query cost. It omits windowing defaults and pagination/limit behavior.

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

Conciseness5/5

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

Two short sentences, no filler, with the usage rule (before search_logs) front-loaded and the return-shape caveat second. Every clause carries information an agent needs.

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?

With no output schema, the description usefully self-documents the return fields and the absence of event bodies. However, for a 4-parameter tool with 25% schema coverage, it leaves the time window and priority semantics entirely unexplained, which is a meaningful gap for correct invocation.

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% — only filter is documented, while start_time, end_time, and the low/high priority enum have no schema text. The description mentions "filter" and "window" only as return fields, giving no format for the time bounds or meaning for priority, so it fails to compensate for the coverage gap.

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

Purpose4/5

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

"Volume check before search_logs" plus "Returns count/filter/window/cpu_ms" makes clear this counts log volume rather than fetching events, and it names the sibling it precedes. The verb is implicit ("volume check" rather than "count"), but the resource and output shape remove ambiguity against search_logs.

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?

"Before search_logs" gives an explicit ordering/selection rule: use this as a pre-flight check prior to the heavier search. It does not state when to skip it or what to do based on the returned count, so it stops short of full when/when-not guidance.

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