Skip to main content
Glama
Sign In
vmware-storage

vmware-storage

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

enable_iscsi

Enables the software iSCSI adapter on an ESXi host, the required prerequisite before adding iSCSI targets. Preview the blast radius first, then apply with confirmation.

Instructions

[WRITE] Enable the software iSCSI adapter (vmhba) on an ESXi host.

Required prerequisite before add_iscsi_target. Without confirm=True this only previews: it returns blast_radius (the host, its current adapters, whether the software adapter already exists) and changes nothing. Show it to the user. Do not set confirm=True on your own because the user asked earlier — they have not seen the preview yet. Already enabled returns action "noop" with the HBA device and IQN. Non-disruptive (no reboot, no impact on existing datastores). Refused when the host's storage view cannot be read. Returns a dict; check state first with get_iscsi_status.

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>"
    },
    "name": "enable_iscsi"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoOptional vCenter/ESXi target name from config.
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
host_nameYesESXi host name exactly as shown in vCenter inventory (FQDN or IP). Errors if not found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • removedInput schema / properties / dry_run
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews.",
-  "title": "Dry Run"
-}
  2. Addedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare write and non-destructive traits, but the description adds substantial operational detail: preview-only default, blast_radius return, noop when already enabled, non-disruptive behavior, and refusal when the storage view is unreadable. None of this is present in structured fields.

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?

The description is front-loaded with the core action and prerequisite, and every sentence carries useful safety or behavioral information. It repeats the confirm preview guidance slightly, preventing a full 5, but contains no fluff.

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

Completeness5/5

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

Despite having no output schema, the description explains the return shape (blast_radius, noop, dict) and tells the agent to check state first via get_iscsi_status. It covers the prerequisite, safety gate, and operational caveats needed to call the tool correctly.

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?

With schema description coverage at 100%, the schema already documents host_name, target, and confirm. The description reinforces confirm's preview semantics but does not add much parameter-specific syntax or edge cases beyond what the schema provides, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Enable the software iSCSI adapter (vmhba) on an ESXi host.' It distinguishes the tool from siblings by naming add_iscsi_target as the dependent operation and get_iscsi_status as the pre-check.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool (required before add_iscsi_target, after checking get_iscsi_status) and gives a strong when-not rule: do not set confirm=True on your own before showing the preview. The workflow routing is unambiguous.

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