Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n

thruk_list_notifications

List notification log entries from Thruk monitoring, with filters for host, service, state, time window, and custom variables.

Instructions

List notification entries from the log (class=3).

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: contact, custom_var, host, hostgroup, service, since, state, 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: # Hosts DOWN in HG_AGILE: {"type":"group","operator":"and","conditions":[ {"type":"leaf","field":"hostgroup","op":"eq","value":"HG_AGILE"}, {"type":"leaf","field":"state","op":"eq","value":"down"} ]} # Hosts in HG_AGILE OR with KERNEL=windows: {"type":"group","operator":"or","conditions":[ {"type":"leaf","field":"hostgroup","op":"eq","value":"HG_AGILE"}, {"type":"leaf","field":"custom_var","op":"eq","value":{"var":"KERNEL","val":"windows"}} ]}
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?

With no annotations supplied, the description must convey behavioral traits. It only mentions 'from the log (class=3)' without stating read-only nature, side effects, or any restrictions. The minimal description fails to provide needed transparency.

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

Conciseness3/5

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

The description is very short (one sentence) and to the point, but it lacks important context that could be added without becoming verbose. Acceptable for conciseness, but could be more informative.

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 8 parameters and no output schema, the description is too sparse. It does not explain the filtering capability, time windows, or return format, leaving the agent with minimal guidance.

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 baseline is 3. The description adds no information about parameters beyond what the schema already provides. It neither enhances nor detracts from schema's parameter documentation.

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?

The description clearly states the tool lists notification entries from a specific log class (class=3), indicating the verb and resource. However, it does not differentiate from similar sibling tools like thruk_notifications or thruk_list_alerts, which could be ambiguous.

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 alternatives such as thruk_notifications or thruk_list_alerts. The description lacks context about the log class or typical use cases.

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