Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_create_contact_group

Create a new contact group in CheckMK by specifying a group name, display alias, and optional members to organize monitoring contacts.

Instructions

➕ Create contact group - Add new contact 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_contact_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesGroup name
aliasYesDisplay alias
membersNoGroup members

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?

No annotations are provided, so the description carries the burden of explaining side effects. It only says 'Add new contact group' and does not mention permissions, duplicate handling, or whether activation of Checkmk changes is required.

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 very brief and front-loaded, but 'Create contact group' and 'Add new contact group' are largely redundant. It contains no unnecessary detail, though the redundancy slightly reduces efficiency.

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?

For a simple create operation with a small schema and no output schema, the description is minimally adequate. However, it omits useful context such as name uniqueness, whether members are required, or whether created groups need activation to take effect.

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 already provides descriptions for all three parameters ('Group name', 'Display alias', 'Group members'), so schema coverage is high. The tool description adds no additional parameter semantics beyond what the schema already states.

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?

Description clearly states 'Create contact group' and 'Add new contact group', identifying the specific verb and resource. It distinguishes this tool from sibling update/delete/retrieve contact group tools.

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 use when creating a new contact group, but it does not explicitly state when not to use it or mention alternatives such as updating or deleting. Usage is inferred from the verb rather than explicitly guided.

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