Skip to main content
Glama
vmware-skills

vmware-storage

by vmware-skills
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

storage_iscsi_remove_target

Destructive

Remove an iSCSI send target from an ESXi host's software iSCSI adapter, then rescan HBAs and VMFS. Verify no datastores depend on it first: LUNs served only by that target become inaccessible.

Instructions

[WRITE] Remove an iSCSI send target from an ESXi host's software iSCSI adapter, then rescan all HBAs and VMFS volumes.

Destructive: LUNs served only by this target become inaccessible after the rescan — first verify the target exists (storage_iscsi_status) and that no datastores depend on it (list_all_datastores). Errors if the address:port pair is not configured or software iSCSI is disabled. Reversible only by re-adding via storage_iscsi_add_target. Audit-logged to ~/.vmware/audit.db. Returns a confirmation string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoConfigured iSCSI TCP port, 1-65535 (default 3260).
targetNoOptional vCenter/ESXi target name from config.
addressYesConfigured iSCSI portal IP (IPv4/IPv6 literal; hostnames rejected). Must match the existing entry exactly.
dry_runNoIf true, return a preview of the change without executing it.
host_nameYesESXi host name as shown in vCenter inventory.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changedv1.8.15
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / address / description
      Added value: +"Configured iSCSI portal IP (IPv4/IPv6 literal; hostnames rejected). Must match the existing entry exactly."
    • addedInput schema / properties / dry_run / description
      Added value: +"If true, return a preview of the change without executing it."
    • addedInput schema / properties / host_name / description
      Added value: +"ESXi host name as shown in vCenter inventory."
    • addedInput schema / properties / port / description
      Added value: +"Configured iSCSI TCP port, 1-65535 (default 3260)."
    • addedInput schema / properties / target / description
      Added value: +"Optional vCenter/ESXi target name from config."
  2. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": false,
+  "title": "Dry Run",
+  "type": "boolean"
+}
  3. First observedv1.3.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses significant behavioral details: the operation triggers an HBA/VMFS rescan, LUNs served only by this target become inaccessible, errors occur for unconfigured pairs or disabled iSCSI, the operation is reversible only by re-adding, and it is audit-logged. This far exceeds what destructiveHint/readOnlyHint already convey.

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 dense but well-organized: action first, then consequences, verification steps, error conditions, reversibility, audit trail, and return type. Every sentence adds useful information, and no fluff is present.

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?

For a destructive mutation tool, the description covers side effects, preconditions, failure modes, recovery, logging, and return behavior. Combined with the schema and annotations, an agent has everything needed to decide whether and how to invoke this 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?

Schema description coverage is 100%, so the baseline is 3. The description does not substantially add parameter-level meaning beyond what the schema already provides, though it does hint that address and port together form the identity of the target.

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 states a specific verb and resource: remove an iSCSI send target from an ESXi host's software iSCSI adapter. It also distinguishes itself from the sibling storage_iscsi_add_target by framing the action as removal and explicitly naming re-adding via that sibling.

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?

The description gives explicit preconditions: verify the target exists with storage_iscsi_status and check datastore dependencies with list_all_datastores. It also states error conditions and the recovery path via storage_iscsi_add_target, giving clear guidance on when and how to use the tool safely.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vmware-skills/VMware-Storage'

If you have feedback or need assistance with the MCP directory API, please join our Discord server