Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n

thruk_list_services

Retrieve a list of monitored services with structured filtering, pagination, and sorting. Filter by host, state, hostgroup, servicegroup, custom variables, and more.

Instructions

List monitored services.

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 'host_name,description'.host_name,description
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, description, host, host_custom_var, hostgroup, servicegroup, state Operators: eq, gte, in, lte, neq, regex 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.
Behavior1/5

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

With no annotations, the description alone must disclose behavioral traits. It fails to mention pagination, authentication requirements, rate limits, or that it returns a list of services. The minimal phrase 'List monitored services' provides no behavioral context beyond the obvious.

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?

The description is extremely concise at four words, front-loading the core action. No wasted words, but could be expanded slightly to improve completeness without losing conciseness.

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

Completeness1/5

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

Given the tool's complexity (6 parameters, nested filters, backends, no output schema), the description is woefully incomplete. It does not explain return format, default sorting, how to paginate, or the filter structure, leaving the agent underinformed.

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?

The input schema documents parameters like filter, sort, and columns with decent descriptions (67% coverage). However, the tool description adds zero value for parameters; it does not even hint at available filtering or sorting capabilities, leaving the agent to rely solely on the schema.

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 'List monitored services' clearly states the verb 'list' and the resource 'monitored services', distinguishing it from sibling tools like thruk_list_hosts or thruk_list_comments. However, it does not elaborate on scope or specifics, preventing a top score.

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_get_service (individual service) or thruk_list_alerts (alerts). The description lacks any context about appropriate use cases or exclusions.

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