Skip to main content
Glama
Sign In
thruk-mcp

thruk-mcp

by k9fr4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

thruk_delete_downtime

Removes a scheduled downtime for a host or service using its unique downtime ID.

Instructions

Delete a host or service downtime by its id.

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": {
      "downtime_id": "<downtime_id>",
      "host": "<host>"
    },
    "name": "thruk_delete_downtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes
serviceNo
backendsNoComma-separated backend names (sites). Omit for all backends.
downtime_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided. The description states a destructive action but offers no behavioral details such as whether the operation is irreversible, permission requirements, or side effects. For a delete 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.

Conciseness4/5

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

The description is a single concise sentence. However, it may be too brief given the tool's complexity; a bit more detail would not hurt.

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 four parameters, no output schema, and no annotations, the description is sparse. It does not explain the relationship between parameters or the expected behavior, leaving ambiguity about why host is required.

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?

Schema description coverage is only 25% (only backends has a description). The description mentions downtime_id but does not clarify the roles of host and service. It fails to explain why host is required despite the claim 'by its id'.

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 (delete), the resource (downtime), and the criterion (by its id). It distinguishes itself from siblings like thruk_delete_active_downtimes and thruk_delete_downtimes_by_filter by specifying deletion by a single ID.

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 like thruk_delete_active_downtimes or thruk_delete_downtimes_by_filter. The description gives no context about prerequisites or exclusions.

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