VMware-AIops

cluster_configure

Adjust cluster HA and DRS settings: enable or disable high availability and distributed resource scheduling, and set DRS behavior to fully automated, partially automated, or manual.

Instructions

[WRITE] Reconfigure cluster HA/DRS settings.

Args: name: Cluster name. ha: Enable (True) or disable (False) HA, or None to leave unchanged. drs: Enable (True) or disable (False) DRS, or None to leave unchanged. drs_behavior: DRS behavior: "fullyAutomated", "partiallyAutomated", or "manual". 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": {
      "name": "<name>"
    },
    "name": "cluster_configure"
  }
}

Input Schema

Name	Required	Description	Default
`ha`	No
`drs`	No
`name`	Yes
`target`	No
`drs_behavior`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.29May 29, 2026
Removedv1.5.28May 22, 2026
Addedv1.5.18May 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate write (readOnlyHint=false). Description adds detail about modifiable settings (HA, DRS, drs_behavior) and target parameter. No mention of side effects or permissions, but adequate given annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with header and list. Every sentence adds value, but could be slightly more compact. Still very clear.

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?

Covers inputs comprehensively. Output schema exists, so return not needed. Lacks mention of preconditions or limitations, but overall sufficient for a reconfig tool.

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

Parameters5/5

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

Schema has 0% coverage, so description fully explains all 5 parameters, including allowed values for drs_behavior and acceptable inputs for ha and drs.

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?

Clearly states 'Reconfigure cluster HA/DRS settings' with specific verb and resource. Differentiates from siblings like cluster_create, cluster_delete, etc.

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?

Purpose is obvious from description, but no explicit when-to-use or exclusionary guidance relative to siblings. Still, the context is clear enough for an agent to infer usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.