Skip to main content
Glama
Sign In
vibeMK

vibeMK

by chexma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vibemk_bulk_update_hosts

Update multiple CheckMK hosts at once with a single request. Streamline host configuration changes by providing a list of update entries to apply in bulk.

Instructions

🔄 Bulk update hosts - Update multiple hosts at once

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": {
      "entries": "<entries>"
    },
    "name": "vibemk_bulk_update_hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYesList of host update entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects, but it only says 'update'. It does not mention whether changes are applied immediately, require activation, are reversible, or how partial failures are handled.

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 one compact sentence with no filler. It communicates the core purpose and scope efficiently.

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

Completeness1/5

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

For a bulk update operation, critical context is missing: the expected payload format for 'entries', what update operations are supported, whether the operation is atomic, and what the response contains. The description is far too thin for practical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'entries' is described only as 'List of host update entries', providing no structure, required fields, or example. The description adds almost no semantic value beyond the parameter name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update') and the resource ('hosts'), and the word 'multiple' signals the bulk scope. However, it does not explicitly differentiate from the singular update_host tool beyond the name.

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?

The description gives no guidance on when to use this bulk operation versus update_host or bulk_create_hosts. It only restates the tool's name without providing selection criteria or examples.

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