Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n

thruk_stale_checks

Identify monitoring checks that have stopped running, revealing false green states to prevent undetected outages.

Instructions

Surface checks that stopped running (the dangerous "false green").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of rows scanned per object type (max 5000, default 500).
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, 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"}} ]}
backendsNoComma-separated backend names (sites). Omit for all backends.
grace_secondsNoAbsolute grace (seconds) added on top of interval*factor / passive_max_age_s to avoid boundary flapping (default 60).
include_hostsNoAlso run the same logic over /hosts host checks (default true).
include_disabledNoReport active checks with active_checks_enabled=0 as reason=disabled (default true).
staleness_factorNoMultiplier on the active check_interval before a check is considered stale (now - last_check > interval*factor + grace_seconds).
passive_max_age_sNoMax age in seconds of a passive check's last result before reason=stale_passive (default 3600).
latency_threshold_sNoLatency in seconds above which a check is flagged with reason=high_latency.
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral details such as configurability via parameters (staleness_factor, grace_seconds), that it can include hosts/disabled checks, or what the output contains.

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?

Single sentence, no fluff. Front-loaded with core purpose, but somewhat under-specified for a tool with 9 parameters.

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?

Tool has 9 parameters and no output schema, but description omits what the result looks like (e.g., a list of checks with reasons). Not complete enough for an agent to fully understand the tool's inputs/outputs.

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 100% with detailed parameter descriptions. The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 it surfaces checks that stopped running (false green), a specific verb+resource. It implies the tool's unique purpose, but doesn't explicitly distinguish from siblings like thruk_checks or thruk_oldest_problems.

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 alternatives. No mention of prerequisites, exclusions, or intended context (e.g., for services vs hosts).

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