Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n

thruk_list_logs

Filter and retrieve Livestatus log entries by host, service, message, and time range with sorting and pagination.

Instructions

Query raw Livestatus log entries (/logs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: a column name, optionally prefixed with '-' for descending (e.g. 'name', '-last_check'); comma-separate multiple keys. Defaults to '-time'.-time
limitNo
sinceNoStart of the time window. Thruk relative time ("-2h", "-7d") or ISO datetime ("2026-05-21 14:00:00"). Omitted = no lower bound.
untilNoEnd of the time window (same formats as since). Default: now.
filterNoStructured filter tree supporting AND/OR nesting. Two node types: leaf: {"type":"leaf", "field":"...", "op":"...", "value":...} group: {"type":"group", "operator":"and"|"or", "conditions":[...]} Available fields: custom_var, host, hostgroup, message, service, since, until Operators: eq, gte, in, lte, neq, regex The 'since'/'until' fields accept Thruk relative time ("-2h", "-7d") or ISO datetime ("2026-05-21 14:00:00"). Examples: # Log entries matching a pattern since -2h: {"type":"group","operator":"and","conditions":[ {"type":"leaf","field":"message","op":"regex","value":"DISK.*CRITICAL"}, {"type":"leaf","field":"since","op":"gte","value":"-2h"} ]}
offsetNo
columnsNoComma-separated columns to return. Omit for a curated default set tuned for this tool; pass '' (empty string) to return all available columns.
backendsNoComma-separated backend names (sites). Omit for all backends.
Behavior2/5

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only states the basic purpose, omitting details such as read-only nature, performance implications, or whether it supports time windows beyond the schema defaults.

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?

The description is a single, front-loaded sentence that efficiently states the tool's purpose. Every word earns its place, and there is no unnecessary verbosity.

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

Completeness2/5

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

Given the complexity (8 parameters, no output schema, many siblings), the description is too sparse. It lacks an overview of what logs are returned, how filtering works, and how it relates to similar tools like thruk_list_alerts.

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 75%, so the schema already documents most parameters well. The description adds no meaning beyond what the schema provides, making it adequate but not improved.

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?

The description clearly states the tool's purpose: 'Query raw Livestatus log entries (/logs).' It uses a specific verb and resource, and implicitly distinguishes from sibling tools like thruk_list_alerts by targeting raw logs.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus its many siblings (e.g., thruk_list_alerts, thruk_list_notifications). The description lacks context about appropriate use cases or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k9fr4n/thruk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server