Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_resource_properties

Read-onlyIdempotent

Retrieve current configuration properties for a VMware resource, including power state, host, vCenter, CPU/memory, and extraConfig flags. Use for configuration facts rather than time-series metrics.

Instructions

[READ] Current property values Aria holds for one resource: power state, parent host and vCenter (summary|parentHost, summary|parentVcenter), configured CPU/memory, extraConfig flags such as config|extraConfig|mem_hotadd. Use this for configuration facts; use get_resource_metrics for time-series values.

Returns a paginated envelope of {name, value} rows sorted by name (value is a string, null when the property carries none), with next_offset — pass it back as offset until null. A failed or unrecognised read is an error, never an empty list; a missing resource is a 404.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, 1-500 (default 100). Out-of-range is rejected.
offsetNoRows to skip; pass the previous response's next_offset.
targetNoAria target name from config; default when omitted.
name_filterNoCase-insensitive substring of the property name, e.g. "summary|".
resource_idYesResource UUID (from list_resources).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.15.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already set readOnlyHint=true, destructiveHint=false, so description doesn't need to repeat that. It adds useful behavioral details: always returns rows (never empty), pages with next_offset, missing resource is a 404. This goes beyond annotations, though it could mention if errors are returned as exceptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well structured: starts with a clear purpose, includes examples inline, and ends with pagination and error behavior. Slightly dense due to inline property paths, but each sentence adds value. No fluff.

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?

Given the tool has 5 params, full schema coverage, and no output schema, the description covers what the tool returns (rows, next_offset, errors), pagination, and error semantics. It's complete for an agent to call it correctly and interpret results.

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 coverage is 100%, so all parameters are documented in the schema. The description adds clarity for offset by mentioning passing back next_offset, and for name_filter by giving an example, but it doesn't explain how target is used beyond 'Aria target name from config'. Baseline 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 clearly states it retrieves current property values for a resource, listing specific categories (power state, parent host, vCenter, CPU/memory, extraConfig flags) and provides example property paths. This distinguishes it from siblings like get_resource_metrics and get_resource.

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 explicitly says to use this for configuration facts and to use get_resource_metrics for time-series values, giving a clear when-to-use and when-not-to-use. This is direct routing to the correct sibling.

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