Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_delete_rule

Delete a CheckMK monitoring rule by providing its rule ID, removing it from the environment configuration.

Instructions

🗑️ Delete rule - Remove monitoring rule

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

Input Schema

NameRequiredDescriptionDefault
rule_idYesRule ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided. The description only says 'remove monitoring rule' without noting that deletion is permanent, irreversible, or may require an activation step.

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?

Extremely concise, just two short phrases. No unnecessary words or repetition.

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

Completeness3/5

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

Provides the essential purpose and parameter, but lacks context about side effects, required permissions, or relationship to activation. Given the minimal nature and lack of annotations, it is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, rule_id, is described in the schema as 'Rule ID to delete', which is clear. The description adds no extra detail but schema coverage is adequate.

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?

Clearly states the action: delete a rule. Distinguishes from sibling rules tools like create_rule, update_rule, and move_rule.

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 or any preconditions. Does not mention whether deletion requires activation or affects other monitoring objects.

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