Skip to main content
Glama
mcp-scalyr-dataset

mcp-scalyr-dataset

by RexySaragih

search_logs

Read-onlyIdempotent

Retrieve a single compact page of matching DataSet/Scalyr log events by applying a tight filter; continue paging with a continuation token.

Instructions

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).

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": "search_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterYesDataSet query language filter (required). Use a field clause such as severity >= 5 or serverHost contains "api". Prefer tight filters after count_logs / list_log_facets.
columnsNoComma-separated columns (default timestamp,severity,serverHost,logfile,message)
end_timeNoEnd time (default 0h)
priorityNolow (default) or high
max_countNoMax events (default 25, hard max 50)
page_modeNohead or tail (default tail)
start_timeNoStart time (default 15m)
continuation_tokenNoOpaque token from a previous page. Requires absolute start_time/end_time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/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 is covered. The description adds behavior the annotations cannot: one page per call, no auto-pagination, and that continuation_token must be used to advance — plus the response format. That is meaningful added context beyond structured fields.

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?

Three tight sentences with zero filler: output shape first, recommended workflow second, pagination constraint last. Front-loaded and every clause carries actionable information.

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

Completeness5/5

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

There is no output schema, so the description compensates by naming the return format, and it fully covers the pagination contract for an 8-parameter tool. Combined with 100% schema coverage, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including filter syntax, defaults, and the max_count hard cap is already documented. The description only echoes the 'tight filter' idea and the continuation-token paging, adding little semantic detail beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Return a small page of matching DataSet/Scalyr log events') and even names the output shape ('compact fenced pipe table'). An agent can distinguish this from count_logs or list_log_facets purely from the description.

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 routes the agent to call count_logs or list_log_facets first and then apply a 'tight filter', which is real workflow guidance rather than a restatement. It does not say when to avoid this tool entirely (e.g. in favor of power_query for aggregation), so it falls short of a full 5.

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