Skip to main content
Glama
Sign In
thruk-mcp

thruk-mcp

by k9fr4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

thruk_delete_active_downtimes

Remove all active downtimes for a host or a specific service. Specify the host name and optionally a service to clear scheduled maintenance periods.

Instructions

Remove ALL currently active downtimes for a host (or one specific service).

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>"
    },
    "name": "thruk_delete_active_downtimes"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
serviceNo
backendsNoComma-separated backend names (sites). Omit for all backends.
retry_on_emptyNoRetry the /downtimes lookup once after a short delay if the first query returns no matches. Works around Naemon's async command pipe (issue #194). Default: True.
retry_delay_secondsNoSeconds to wait before the retry when retry_on_empty=True. Set to 0 to disable the wait. Default: 2.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It states it 'Remove' (destructive), but does not disclose permissions required, reversibility, or side effects like whether all downtimes are removed permanently without confirmation. Minimal behavioral detail beyond the action.

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, concise sentence (12 words) that front-loads the action and scope. Every word adds value, and there is no extraneous information.

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

Completeness4/5

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

For a deletion tool, the description covers the core function and target. However, it lacks information about return values (e.g., success message, count of deleted downtimes) and does not specify if the operation is atomic. Nearly complete but missing return context.

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 60%; the description adds context for 'host' and 'service' (targets a host or one service) but does not explain other parameters like retry_on_empty or retry_delay_seconds beyond what the schema provides. The description adds moderate value beyond the schema.

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 action 'Remove', scope 'ALL currently active downtimes', and target 'for a host (or one specific service)'. It effectively distinguishes from sibling tools like thruk_delete_downtime (single) and thruk_delete_downtimes_by_filter (filtered).

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 bulk removal of all active downtimes for a host or service, but does not explicitly state when to use this tool versus alternatives such as thruk_delete_downtime or thruk_delete_downtimes_by_filter. No when-not or context 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