Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_delete_service_group

Deletes a specified service group from CheckMK using its name, simplifying monitoring configuration.

Instructions

🗑️ Delete service group - Remove a service group from CheckMK

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

Input Schema

NameRequiredDescriptionDefault
nameYesService group name to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the burden of disclosing side effects. It simply states 'Remove a service group from CheckMK' without mentioning potential cascading effects, reversibility, or confirmation requirements. This lacks transparency for a destructive operation.

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 one concise sentence that immediately conveys the purpose. It is well-structured, front-loaded, and contains no unnecessary words.

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 simple delete operation with one parameter and no output schema, the description is sufficiently complete. It could mention that deletion is permanent or that it affects only the service group, but these are not critical for basic usage.

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?

The single parameter 'name' is described as 'Service group name to delete', which aligns with the schema and adds slight context. Schema coverage is 100%, so baseline is 3; the description does not significantly enhance 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 (delete) and the resource (service group) in CheckMK, distinguishing it from other service group operations like create or update. It is specific and unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., update service group, bulk delete). It does not mention conditions, prerequisites, or situations where deletion is appropriate.

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