Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

list_resources

Read-onlyIdempotent

Filter Aria Operations resources by name or kind to get the UUID needed by other tools. Paginated results include a truncated flag, so verify before treating the set as complete.

Instructions

[READ] List resources in Aria Operations filtered by kind. Start here: this turns a name or kind into the UUID other resource tools need. Then call get_resource for detail on one row.

Returns a paginated envelope: items, returned, limit, total (null when the API reports no size), truncated, hint. Check truncated before calling this the complete set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results. Default 100. Paginated automatically, so a larger limit spans more than one page.
targetNoAria target name from config; default when omitted.
name_filterNoSubstring filter on resource name (case-insensitive).
resource_kindNoe.g. VirtualMachine, HostSystem, ClusterComputeResource, Datastore, Datacenter.VirtualMachine

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.10.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results. Default 100. Paginated automatically, so a larger limit spans more than one page."
    • addedInput schema / properties / name_filter / description
      Added value: +"Substring filter on resource name (case-insensitive)."
    • addedInput schema / properties / resource_kind / description
      Added value: +"e.g. VirtualMachine, HostSystem, ClusterComputeResource, Datastore, Datacenter."
    • addedInput schema / properties / target / description
      Added value: +"Aria target name from config; default when omitted."
  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_resourcesOutput",
-  "type": "object"
-}New value: +null
  3. Addedv1.5.29
  4. Removedv1.5.28
  5. First observedv1.3.2

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the description adds value by disclosing pagination behavior and the exact response envelope: items, returned, limit, total, truncated, and hint. The warning to 'check truncated before calling this the complete set' is useful behavioral context beyond the schema.

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 front-loaded with the most important guidance: this is a read operation and the entry point for UUID resolution. Every sentence earns its place, including the paginated envelope details and the truncated check warning.

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 appropriately covers the return envelope and pagination semantics. Combined with 100% schema parameter coverage and annotations, the description gives an agent everything needed to invoke and interpret this tool correctly.

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%, with each parameter already documented. The description reinforces the resource_kind filter but adds no new parameter-level semantics beyond what the schema provides, 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 states a specific verb and resource: 'List resources in Aria Operations filtered by kind.' It differentiates itself from get_resource by explicitly saying 'Start here: this turns a name or kind into the UUID other resource tools need' and routing the agent to 'get_resource for detail on one row.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage context: it is the entry point for resolving a name or kind into a UUID for downstream resource tools, and it directs the agent to get_resource next. It does not enumerate exclusions relative to sibling tools, but the guidance is sufficiently directional for correct selection.

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