Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_create_user

Creates a new user in CheckMK monitoring with configurable username, full name, email, roles, password, and contact groups.

Instructions

👤 Create user - Add new CheckMK user

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": {
      "username": "<username>",
      "fullname": "<fullname>"
    },
    "name": "vibemk_create_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail address
rolesNoUser roles
fullnameYesFull name
passwordNoPassword
usernameYesUsername
contactgroupsNoContact groups to assign user to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

B3/5.0
Behavior1/5

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

No annotations provided; description is minimal and does not disclose side effects (e.g., whether creation triggers activation, whether it overwrites existing users, or permission requirements). The single verb 'Add' gives no behavioral transparency.

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?

One-line description is concise and free of filler; it is appropriately short for a simple create operation.

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 create tool with no annotations or output schema, the description lacks necessary context such as what happens after creation (activation required?), error handling, or relationships to other objects. Incomplete.

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?

Schema covers all 6 parameters with descriptions; description adds no additional parameter semantics beyond the schema. Baseline 3 applies.

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?

States a specific verb 'Create' and resource 'user' with 'Add new CheckMK user' - unambiguous and distinguishes from sibling tools like update/delete/get.

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 versus update_user or delete_user, nor any prerequisites (e.g., existing contact groups or roles). Implied only by 'new'.

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