Skip to main content
Glama
Sign In
thruk-mcp

thruk-mcp

by k9fr4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

thruk_service_availability

Compute service availability as uptime/SLA percentage over a custom time window. Supports time periods, downtimes, and soft states.

Instructions

Compute availability (uptime / SLA %) for a service over a configurable time window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>",
      "service": "<service>"
    },
    "name": "thruk_service_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesHost name
sinceNoStart of analysis window. Thruk relative time ("-7d", "-1m") or ISO datetime ("2026-05-01 00:00:00"). Default: last 7 days. Ignored when ``timeperiod`` is set.-7d
untilNoEnd of analysis window (same formats as ``since``). Defaults to now. Ignored when ``timeperiod`` is set.
serviceYesService description
backendsNoComma-separated backend names (sites). Omit for all backends.
timeperiodNoThruk-native time period shortcut: "last24hours", "lastweek", "lastmonth", "thismonth", etc. Overrides ``since``/``until`` when provided.
with_downtimesNoCount scheduled downtime periods as outages (withdowntimes=1).
include_soft_statesNoInclude soft state changes in calculations (includesoftstates=1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided. The description only states what the tool computes without disclosing behavioral traits such as side effects, performance implications, or required permissions. For a compute-heavy tool, this is insufficient.

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

Conciseness5/5

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

The description is a single sentence that concisely captures the core functionality and its main configurable aspect (time window). It is front-loaded with the key verb and resource.

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?

With 8 parameters and no output schema, the description lacks context on the return format, calculation details, or how parameters like `with_downtimes` affect results. It is too brief to be fully informative.

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%, so the description does not need to add parameter details. The description adds no extra meaning beyond what the input schema already provides, achieving baseline adequacy.

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 uses a specific verb 'Compute' and clearly identifies the resource 'availability for a service' with output type 'uptime / SLA %' and configurable time window. This distinguishes it from sibling tools like thruk_host_availability or thruk_hostgroup_availability which operate on different resource types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for service-level availability computations but provides no explicit guidance on when to use this tool versus alternative tools (e.g., host or hostgroup availability) or when not to use it. No context about prerequisites or limitations is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools