Skip to main content
Glama
k9fr4n

thruk-mcp

by k9fr4n

thruk_reliability_report

Calculate reliability metrics like MTTR, MTBF, and incident counts for hosts and services from monitoring logs using structured filters and time windows.

Instructions

Per host/service reliability metrics (MTTR / MTBF / incidents) from the log.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of host/service objects to return (busiest first, default 50).
sinceNoStart of analysis window. Thruk relative time ("-30d", "-7d") or ISO datetime ("2026-05-21 14:00:00"). Default: last 30 days.-30d
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, service 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.
Behavior3/5

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

No annotations provided, so description carries full burden. It says 'from the log,' implying a read-only operation, but does not explicitly state side effects, performance implications, or limitations. This is adequate but not thorough.

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 a single efficient sentence, but it is too short given the complexity of the tool. It could include a brief note on output or usage context without sacrificing front-loading.

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?

No output schema provided. The description does not explain the format of the returned reliability metrics, ordering (busiest first implied by limit description but not stated), or aggregation level. This leaves ambiguity for agent invocation.

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 100% with thorough parameter descriptions (e.g., filter with examples). The tool description adds no extra meaning beyond the schema, so baseline score of 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 provides per host/service reliability metrics (MTTR, MTBF, incidents) from logs. This uniquely distinguishes it from sibling tools like thruk_incident_timeline which focuses on timeline of incidents, not aggregated metrics.

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. The description does not mention prerequisites, exclusions, or typical use cases, leaving the agent to infer from the tool name alone.

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