Skip to main content
Glama
vmware-skills

vmware-storage

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

browse_datastore

Read-onlyIdempotent

Recursively search a VMware datastore folder and its subfolders for files matching a glob pattern, returning each match plus total counts to locate arbitrary files.

Instructions

[READ] Search a datastore folder and all its subfolders for files.

Use this for arbitrary files or a glob; prefer scan_datastore_images for deployable images. datastore_name comes from list_all_datastores.

Returns the list envelope: 'items' holds one row per file, and 'returned'/'total'/'truncated' state whether the listing is complete. All matches are returned, so truncated is always false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoDatastore-relative folder to start from (empty for root); a leading '/' or '..' is refused. The search is recursive, so the root returns matches from every folder; each row's ds_path is "[ds] dir/file".
targetNoOptional vCenter/ESXi target name from config.
patternNoGlob pattern to filter files (e.g. "*.ova", "*.iso").*
datastore_nameYesDatastore name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • changedInput schema / properties / path / description
      Previous value: -"Subdirectory path (empty for root)."New value: +"Datastore-relative folder to start from (empty for root); a leading '/' or '..' is refused. The search is recursive, so the root returns matches from every folder; each row's ds_path is \"[ds] dir/file\"."
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / datastore_name
      Added value: +{
+  "description": "Datastore name.",
+  "title": "Datastore Name",
+  "type": "string"
+}
    • removedInput schema / properties / ds_name
      Removed value: -{
-  "description": "Datastore name.",
-  "title": "Ds Name",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "ds_name"
-]New value: +[
+  "datastore_name"
+]
  3. Changed5 schema fields changedv1.8.15
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / ds_name / description
      Added value: +"Datastore name."
    • addedInput schema / properties / path / description
      Added value: +"Subdirectory path (empty for root)."
    • addedInput schema / properties / pattern / description
      Added value: +"Glob pattern to filter files (e.g. \"*.ova\", \"*.iso\")."
    • addedInput schema / properties / target / description
      Added value: +"Optional vCenter/ESXi target name from config."
  4. 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": "browse_datastoreOutput",
-  "type": "object"
-}New value: +null
  5. 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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real behavioral context beyond them: the search is recursive by default, the response is a list envelope with items/returned/total/truncated, and truncation never occurs because all matches are returned.

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 with the '[READ]' marker and the core action, then the routing guidance, then the setup hint, then the return contract. Four short sentences, no filler, nothing repeated from the 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?

There is no output schema, so the description carries the burden of explaining return values — and it does, describing the list envelope fields and the truncation invariant. With 4 params at full schema coverage and declared annotations, nothing an agent needs to call this correctly is missing.

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 path/pattern/target semantics are already documented in the schema and the baseline is 3. The description adds provenance meaning beyond the schema by stating datastore_name comes from list_all_datastores, and reinforces the recursive-glob behavior that ties pattern usage together.

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 opens with a specific verb+resource+scope: '[READ] Search a datastore folder and all its subfolders for files.' It explicitly distinguishes itself from the sibling scan_datastore_images by naming it, so an agent can route without opening a second 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?

It states when to use this tool ('arbitrary files or a glob') and names the preferred alternative for the other case ('prefer scan_datastore_images for deployable images'). It also tells the agent where the required datastore_name value comes from (list_all_datastores), closing the setup loop.

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