Skip to main content
Glama
Sign In
vmware-storage

vmware-storage

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_cached_images

Read-onlyIdempotent

List deployable OVA/OVF/ISO/VMDK images from the local cache registry without a vCenter connection or datastore I/O. Filter cached results by target, datastore, or image type.

Instructions

[READ] List deployable images (OVA/OVF/ISO/VMDK) from the local cache registry — instant, no vCenter connection or datastore I/O.

Reads ~/.vmware-storage/image_registry.json, which scan_datastore_images fills; results may be stale, and are empty until a scan has run. For a live listing use scan_datastore_images instead. Returns the list envelope: 'items' holds {target, datastore, name, ds_path, size_mb, type, modified} and is empty if nothing matches, while 'returned'/'total'/'truncated' state whether the listing is complete. The whole registry is filtered in memory, so truncated is always false.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cached_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoOnly rows scanned from this vCenter/ESXi target (a name from config, as scan_datastore_images takes; an unknown name is refused with the configured ones). Rows cached before rows recorded their target appear only when this is omitted. Omit for every target.
datastoreNoFilter by exact datastore name. Omit for all datastores.
image_typeNoFilter by file extension without the dot, e.g. "ova", "iso", "ovf", "vmdk" (case-insensitive). Omit for all types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • addedInput schema / properties / target
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only rows scanned from this vCenter/ESXi target (a name from config, as scan_datastore_images takes; an unknown name is refused with the configured ones). Rows cached before rows recorded their target appear only when this is omitted. Omit for every target.",
+  "title": "Target"
+}
  2. Changed3 schema fields changedv1.8.15
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / datastore / description
      Added value: +"Filter by exact datastore name. Omit for all datastores."
    • addedInput schema / properties / image_type / description
      Added value: +"Filter by file extension without the dot, e.g. \"ova\", \"iso\", \"ovf\", \"vmdk\" (case-insensitive). Omit for all types."
  3. Changed1 schema field changedv1.8.9
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_cached_imagesOutput",
-  "type": "object"
-}New value: +null
  4. First observedv1.3.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description nonetheless adds real behavior: it reads ~/.vmware-storage/image_registry.json, may be stale, is empty until a scan runs, and is filtered entirely in memory so 'truncated' is always false. This is substantially more than the annotations 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?

Front-loaded '[READ]' tag and one-line purpose, followed by the data-source caveat and the return-envelope semantics. Every sentence carries distinct information; nothing is redundant with the name or schema.

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?

No output schema exists, but the description supplies the return contract (items holding {target, datastore, name, ds_path, size_mb, type, modified}, plus returned/total/truncated). Combined with full param coverage and annotations, an agent has everything needed to call and interpret it.

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 schema already documents target/datastore/image_type in depth. The description adds only an indirect note that the whole registry is filtered in memory, which does not add per-parameter meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb (List) plus resource (deployable images OVA/OVF/ISO/VMDK) and scope (from the local cache registry). It explicitly distinguishes itself from the sibling scan_datastore_images, so an agent can route correctly without opening either schema.

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?

Names the alternative (scan_datastore_images) and the condition that selects it ('For a live listing use scan_datastore_images instead'). It also states the cache is populated by a prior scan and may be stale/empty until one has run, giving clear when-and-when-not guidance.

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