Skip to main content
Glama
vmware-skills

vmware-storage

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

list_cached_images

Read-onlyIdempotent

Retrieve deployable images (OVA/OVF/ISO/VMDK) from local cache registry without vCenter or datastore I/O. Filter by datastore or image type to quickly view previously scanned inventory.

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, populated by prior datastore scans; results may be stale or empty if no scan has run. For a live listing use scan_datastore_images instead. Returns the list envelope: 'items' holds {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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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. 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."
  2. 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
  3. First observedv1.3.2

TDQS

A4.9/5.0
Behavior5/5

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

Discloses that the tool reads ~/.vmware-storage/image_registry.json, performs no vCenter/datastore I/O, filters in memory, and always reports truncated as false. These details go well beyond the annotations, which already mark the operation as read-only, idempotent, and non-destructive.

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-organized: purpose, source/staleness, live alternative, and return envelope. Every sentence carries non-redundant information needed for correct tool selection and invocation, with key facts front-loaded.

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 read-only, zero-required-param tool with no output schema, the description fully explains the data source, staleness behavior, filter semantics, and exact return envelope fields. An agent can accurately predict output for omitted filters and handle empty or incomplete results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3 because both parameters already have descriptions. The tool description adds that the entire registry is filtered in memory and that truncation is impossible, which clarifies how the optional filters affect results.

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) and resource (deployable images) and scopes it to the local cache registry, clearly distinguishing it from live datastore operations. The [READ] prefix and explicit image types make the tool's purpose unmistakable.

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?

Explicitly names scan_datastore_images as the alternative when a live listing is needed, and warns that cached results may be stale or empty if no prior scan has run. This gives an agent concrete selection criteria beyond the tool name.

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