Skip to main content
Glama
Sign In
thruk-mcp

thruk-mcp

by k9fr4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

thruk_delete_comment

Delete a host or service comment from Thruk monitoring using its numeric ID.

Instructions

Delete a host or service comment 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": {
      "comment_id": "<comment_id>",
      "host": "<host>"
    },
    "name": "thruk_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesHost name owning the comment.
serviceNo
backendsNoComma-separated backend names (sites). Omit for all backends.
comment_idYesNumeric comment id (as returned by thruk_list_comments).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states deletion but does not disclose error handling (e.g., missing comment), permission requirements, or side effects. Minimal transparency beyond the action itself.

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?

A single sentence that is directly informative with no unnecessary words or repetition. Efficiently conveys the core action.

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?

For a deletion tool with 4 parameters and no output schema, the description lacks essential context: expected behavior on success/failure, error types, required permissions, and relationship to other tools (e.g., list_comments for obtaining an id). The description is too minimal for a complete understanding.

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 coverage is 75% (host, backends, comment_id have descriptions). The description adds no extra meaning beyond the schema; the 'by its id' phrase is redundant with the comment_id parameter description. The 'service' parameter lacks a schema description and no additional clarity is provided.

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) and the resource (host or service comment by its id). It is specific and distinguishes from sibling tools like thruk_add_comment or thruk_list_comments.

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 prerequisites (e.g., comment must exist, id from list_comments), and no exclusion criteria. The agent is left to infer usage context.

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