Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_create_host_group

Create a host group in CheckMK by providing a group name and display alias, enabling organized grouping of monitored hosts.

Instructions

➕ Create host group - Add new host group

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

Input Schema

NameRequiredDescriptionDefault
nameYesGroup name
aliasYesDisplay alias

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It accurately describes a write operation but does not disclose potential side effects, failure conditions (e.g., name conflicts), or permission requirements. The behavior is unsurprising for a create operation, but transparency is limited.

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 extremely concise, using two short phrases that convey the purpose without redundancy. No unnecessary words or details.

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

Completeness5/5

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

Given the simplicity of the operation and the lack of an output schema, the description is complete for an agent to understand what the tool does. No additional context about return values or complex behavior is needed.

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 input schema covers 100% of parameters with simple descriptions ('Group name', 'Display alias'), and the description does not add additional semantics beyond the schema. Since the schema fully describes the parameters, a baseline of 3 is appropriate.

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 ('Create host group' / 'Add new host group') and the resource ('host group'). It is unambiguous and distinguishes from sibling tools like update_host_group, delete_host_group, and get_host_groups.

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 (use to create a host group) but does not explicitly mention when not to use it or contrast with alternatives such as bulk creation or updating an existing group. The name and context make the purpose clear, but there is no explicit guidance.

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