Skip to main content
Glama
vmware-skills

vmware-storage

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_all_datastores

Read-onlyIdempotent

[READ] List all datastores with capacity, usage percentage, and accessibility.

Instructions

[READ] List all datastores with capacity, usage percentage, and accessibility.

Use this first for the datastore_name that browse_datastore and scan_datastore_images require.

Returns the list envelope: 'items' holds one row per datastore, and 'returned'/'total'/'truncated' state whether the listing is complete. Every datastore is enumerated before limit is applied, so total is the real count and truncated is true only when limit cut rows off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax datastores to return (None = all).
targetNoOptional vCenter/ESXi target name from config.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Max datastores to return (None = all).",
+  "title": "Limit"
+}
  2. Changed2 schema fields changedv1.8.15
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / target / description
      Added value: +"Optional vCenter/ESXi target name from config."
  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_all_datastoresOutput",
-  "type": "object"
-}New value: +null
  4. First observedv1.3.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: enumeration happens before limit is applied, so 'total' is the real count and 'truncated' is only true when limit cut rows off. That pagination semantics is real value beyond the annotations, though it stops short of explaining default limit or the accessibility field's meaning.

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-loads the [READ] marker and the core action, then the workflow routing, then return-shape semantics. Three tight sentences with no filler; every clause carries information the agent uses.

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?

There is no output schema, and the description compensates by documenting the list envelope (items, returned, total, truncated). Combined with the routing guidance and the 100%-covered input schema, an agent has everything needed to call this correctly and interpret the result.

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% (both params documented), so the baseline would be 3, but the description goes further by explaining the interaction between 'limit' and the returned total/truncated values. It clarifies that total reflects the full enumeration rather than the truncated list, which meaningfully disambiguates the limit parameter. It adds nothing about 'target', hence not a 5.

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 (datastores), and names the exact fields returned (capacity, usage percentage, accessibility). It also distinguishes itself from siblings by naming browse_datastore and scan_datastore_images as downstream consumers, so an agent can place it in the workflow without opening any 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?

Explicitly says 'Use this first for the datastore_name that browse_datastore and scan_datastore_images require', which names both the alternative tools and the condition that selects this one. The sequencing guidance (call this before the others) is exactly the when-to-use signal an agent needs.

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