Skip to main content
Glama
Sign In
VMware-AIops

VMware-AIops

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cluster_remove_host

Destructive

Remove an ESXi host from a vSphere cluster. The host must be in maintenance mode.

Instructions

[WRITE] Remove a host from a cluster (host must be in maintenance mode).

Args: cluster_name: Cluster to remove the host from. host_name: ESXi host name to remove. target: Optional vCenter target name from config.

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": {
      "cluster_name": "<cluster_name>",
      "host_name": "<host_name>"
    },
    "name": "cluster_remove_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo
host_nameYes
cluster_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.29
  2. Removedv1.5.28
  3. Addedv1.5.18

TDQS

A4.2/5.0
Behavior4/5

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

The description aligns with annotations (readOnlyHint=false, destructiveHint=true) by prefixing with '[WRITE]' and detailing removal. It adds context about the maintenance mode requirement, which annotations do not cover. No contradictions.

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 very concise (two sentences plus parameter list) and front-loaded with the action and condition. Every sentence adds value.

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 covers the key prerequisite and parameter semantics. With an output schema present, return values are not needed. However, it does not mention error conditions if the host is not in maintenance mode, which would be helpful for complete context.

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?

Given 0% schema description coverage, the description provides basic explanations for each parameter (e.g., 'Cluster to remove the host from'). However, it lacks detail on formatting or constraints, and the description for target is minimal.

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 ('Remove a host from a cluster') and the necessary condition ('host must be in maintenance mode'). It effectively distinguishes this from sibling tools like cluster_add_host.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a clear prerequisite (maintenance mode) but does not explicitly mention when not to use this tool or suggest alternatives. It implicitly differentiates from sibling tools focused on adding hosts.

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