Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n

thruk_list_comments

Fetch comments and acknowledgements for hosts and services with support for filtering by host, hostgroup, or custom variables, and sorting by entry time.

Instructions

List comments (acknowledgements appear here too).

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 '-entry_time'.-entry_time
limitNo
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 Operators: eq, gte, in, lte, neq, regex Examples: # Objects in HG_AGILE: {"type":"leaf","field":"hostgroup","op":"eq","value":"HG_AGILE"} # 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, the description must disclose behavior. It only notes that acknowledgements appear, but omits that the operation is read-only, how filtering/pagination affects output, or any side effects.

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

Conciseness4/5

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

Description is a single concise sentence with no waste. However, it could include more useful information without becoming verbose.

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 6 parameters, no output schema, and no annotations, the description is too short. It lacks information about return format, offset/limit pagination behavior, and the nature of comment objects.

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 coverage is 67% (4 of 6 parameters have descriptions). The description adds no extra parameter information beyond what the schema already provides, so baseline 3 is appropriate.

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 lists comments and explicitly mentions that acknowledgements are included. It distinguishes from sibling tools like add/delete comment.

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 on when to use this tool versus similar list tools (e.g., list_downtimes, list_alerts). Missing context about prerequisites 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