Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_move_host

Move a CheckMK host to another folder using its name and target path. Reorganize your monitoring structure by relocating hosts between folders.

Instructions

📁 Move host - Move host to different folder

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": {
      "host_name": "<host_name>",
      "target_folder": "<target_folder>"
    },
    "name": "vibemk_move_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_nameYesName of the host
target_folderYesTarget folder path

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 are provided, so the description bears the burden of disclosing side effects. It only implies a mutation (moving) but does not mention activation changes, reversibility, or other behavioral impacts.

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, immediately stating the verb and object. The emoji adds a slight visual cue but does not detract. Every word serves to communicate the purpose.

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 move operation, the description is sufficient to understand what it does, but it lacks context about post-action requirements (e.g., activation) or return behavior. No output schema exists, so some context is missing.

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 schema already covers both parameters with basic descriptions. The tool description adds no further meaning, such as format expectations for folder paths or host names. Baseline 3 for high schema coverage.

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 (move host) and the resource (host) with the destination (different folder). It is unambiguous and distinct from sibling tools like move_folder or update_host.

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 use case is implied by the description (move a host to a different folder) but no explicit guidance is given about when to prefer this over alternatives like move_folder or update_host.

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