Skip to main content
Glama
vmware-skills

vmware-storage

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

storage_iscsi_add_target

Add an iSCSI send (dynamic discovery) target to an ESXi host's software iSCSI adapter, then rescan all HBAs and VMFS volumes to discover new LUNs.

Instructions

[WRITE] Add an iSCSI send (dynamic discovery) target to an ESXi host's software iSCSI adapter, then automatically rescan all HBAs and VMFS volumes to discover new LUNs.

Prerequisite: software iSCSI must be enabled first (storage_iscsi_enable); otherwise returns an error with guidance. Idempotent: a duplicate address:port returns "already configured" without changes. No separate storage_rescan call is needed afterwards. Audit-logged to ~/.vmware/audit.db. Returns a confirmation string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portNoiSCSI TCP port, 1-65535 (default 3260).
targetNoOptional vCenter/ESXi target name from config.
addressYesiSCSI portal IP address (IPv4/IPv6 literal; hostnames are rejected with a validation error).
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.

  1. Changed6 schema fields changedv1.8.15
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / address / description
      Added value: +"iSCSI portal IP address (IPv4/IPv6 literal; hostnames are rejected with a validation error)."
    • 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: +"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

A3.8/5.0
Behavior1/5

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

The description provides rich behavioral context such as [WRITE], automatic rescanning, audit logging, and return behavior. However, it explicitly claims 'Idempotent' while the annotations set idempotentHint to false, which is a direct contradiction and forces a low score.

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 compact and well-structured: core action first, then prerequisite, idempotency, rescan implication, audit trail, and return type. Every sentence earns its place and there is no filler.

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?

For a write operation with five parameters and a complete schema, the description covers prerequisites, side effects, idempotency, audit logging, and return behavior, so an agent can call it correctly. The contradictory idempotency metadata introduces avoidable uncertainty and prevents a perfect completeness score.

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%, and each parameter already has a meaningful schema description including defaults and validation intent. The description adds the address:port duplicate semantics but does not substantially increase parameter-level understanding beyond the schema, 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 uses a specific verb ('Add') and names the exact resource: an iSCSI send (dynamic discovery) target on an ESXi host's software iSCSI adapter. It also clearly distinguishes itself from sibling tools like storage_iscsi_enable, storage_iscsi_remove_target, and storage_rescan.

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 prerequisite storage_iscsi_enable is explicitly named, including the failure behavior if it is not met. It also tells the agent that no separate storage_rescan is needed, giving clear routing guidance relative to siblings.

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