Skip to main content
Glama
vmware-skills

vmware-storage

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

storage_iscsi_remove_target

Destructive

Remove an iSCSI send target from an ESXi host's software adapter, previewing affected paths and datastores before confirming the destructive rescan.

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 through this target become inaccessible after the rescan. Without confirm=True this only previews: it returns blast_radius (the static targets it discovered, the paths that go with them, the devices and VMFS datastores that lose all or some paths) and changes nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user asked earlier — they have not seen what it cuts off yet. Refused when a datastore would lose every path (unmount it first), when the address:port is not configured or software iSCSI is disabled, and when any path or static target cannot be attributed. Reversible only by re-adding via storage_iscsi_add_target. Returns a dict.

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.
confirmNoFalse (default) returns the blast radius and changes nothing. True applies it.
dry_runNoDeprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews.
host_nameYesESXi host name as shown in vCenter inventory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.11.0
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "description": "False (default) returns the blast radius and changes nothing. True applies it.",
+  "title": "Confirm",
+  "type": "boolean"
+}
    • addedInput schema / properties / dry_run / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / dry_run / default
      Previous value: -falseNew value: +null
    • changedInput schema / properties / dry_run / description
      Previous value: -"If true, return a preview of the change without executing it."New value: +"Deprecated alias for confirm; removed in the next minor release. dry_run=False acts, dry_run=True previews."
    • removedInput schema / properties / dry_run / type
      Removed value: -"boolean"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "storage_iscsi_remove_targetOutput",
-  "type": "object"
-}New value: +null
  2. 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."
  3. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": false,
+  "title": "Dry Run",
+  "type": "boolean"
+}
  4. First observedv1.3.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already signal write/destructive behavior, but the description adds concrete behavioral detail: preview mode semantics, LUN inaccessibility after rescan, side-effect rescanning, refusal guardrails, and reversibility. This goes well beyond destructiveHint.

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 long but every sentence is high-signal for a destructive mutation tool: operation, preview mode, consent rule, refusal conditions, reversal, and return type. It is front-loaded with the action and the [WRITE] marker.

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 6-parameter tool with no output schema, it is complete enough: it describes the blast_radius return contents, refusal conditions, required user confirmation, and reversal path. The schema carries the remaining parameter details.

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 reinforces confirm's preview/apply behavior and the address:port prerequisite, but most parameter meaning is already provided by the schema.

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 names the exact operation: removing an iSCSI send target from an ESXi software iSCSI adapter and rescanning HBAs/VMFS. It also distinguishes itself from adjacent siblings by naming storage_iscsi_add_target as the reversal path.

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 gives explicit invocation policy: without confirm=True this only previews, the result must be shown to the user, and the agent must not set confirm=True on its own. It also lists refusal conditions and the only reversal path, so an agent knows when not to proceed.

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