Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_create_user_role

Clone an existing role to create a new custom user role in CheckMK. Specify a new role ID and optional alias, using an existing role as the permission template.

Instructions

➕ Create user role - Clone an existing role to create a new custom role

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": {
      "base_role_id": "<base_role_id>",
      "new_role_id": "<new_role_id>"
    },
    "name": "vibemk_create_user_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_aliasNoDisplay name/alias for the new role
new_role_idYesID for the new role
base_role_idYesExisting role ID to clone from (e.g., 'admin', 'user', 'guest')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are present, and the description only indicates that the tool creates a role by cloning. It does not disclose side effects, permission requirements, failure modes, or whether the operation is idempotent.

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 a single concise sentence that directly conveys the tool's purpose and method, with no redundant or extraneous wording.

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?

The description and schema together give enough context for a basic invocation: which role to clone and what ID to assign. It does not specify output behavior, but for a simple create operation this is acceptable.

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 provides clear descriptions for all three parameters, including an example for base_role_id. The description adds no extra meaning beyond the schema, so the score stays at the baseline.

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 a specific action: create a user role by cloning an existing role. It distinguishes this tool from list/show/update/delete role siblings by emphasizing the clone-and-create behavior.

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?

Description implies the tool is for creating a new role from an existing one, but it does not explicitly state when to prefer this over other role-related tools, nor does it mention prerequisites or alternative workflows.

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