Skip to main content
Glama
mcp-scalyr-dataset

mcp-scalyr-dataset

by RexySaragih

list_log_facets

Read-onlyIdempotent

List top values for a log field so you can choose valid filters before narrowing log searches.

Instructions

Top values for one field (hosts, files, severity). Use before narrowing search_logs filters.

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>",
      "field": "<field>"
    },
    "name": "list_log_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesField to facet (e.g. serverHost, logfile)
filterYesDataSet filter (required non-empty)
end_timeNo
priorityNo
max_valuesNoMax facet values (default 20, hard max 50)
start_timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 the safety profile is fully covered structurally. The description adds the workflow context of being a pre-filter step, but says nothing about result ordering, cardinality behavior, or truncation beyond the max_values note already in the schema. With annotations carrying the behavioral weight, a 3 is appropriate.

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, front-loaded with the purpose and followed by the usage rule; there is no filler. Every clause carries information the agent needs to decide and call.

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 six-parameter read tool with no output schema, the definition leaves real gaps: how start_time/end_time and priority alter results, and whether the response is a value/count list. The core intent and workflow placement are present, so it is adequate but incomplete.

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 coverage is only 50%: field, filter and max_values are documented, but start_time, end_time and priority are undocumented in both schema and description. The description does not compensate, and its field examples ("hosts, files, severity") do not match the schema's examples (serverHost, logfile), leaving the agent unsure what values field accepts.

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?

"Top values for one field" is a specific verb+resource statement, and the parenthetical examples (hosts, files, severity) concretize what a facet is. It is distinguishable from search_logs/count_logs by implication, but the description never explicitly contrasts itself with those siblings.

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?

"Use before narrowing search_logs filters" gives a clear when-to-use condition and names the downstream tool it feeds. It stops short of stating when not to use it (e.g. when cardinality is already known or when a full search is required).

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