Skip to main content
Glama

vme_list_clouds

List clouds and zones configured in HPE VME to see which hypervisor targets, such as KVM or VMware, the platform manages. Filter by gateway when needed.

Instructions

List all clouds/zones configured in HPE VME.

A cloud in Morpheus represents a hypervisor target: KVM (VME native), VMware vSphere, or any other supported provider. This shows what infrastructure VME is managing.

Args: gateway_id: Target gateway (optional).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vme_list_clouds"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. "List" implies read-only, but it says nothing about pagination, result ordering, permissions/auth needs, or what the returned cloud records contain, all of which matter for a discovery call with no output schema.

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?

The text is front-loaded with the core action and kept to three short sentences with no filler. The middle explanatory sentence about hypervisor targets is useful context rather than padding, though it is slightly more conceptual detail than a list call strictly needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-optional-param list tool with no annotations or output schema, the description covers purpose and conceptual scope adequately. It stops short of the details an agent would still need: return shape, whether results are filtered by gateway, and the identifier format.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter is only annotated as "Target gateway (optional)," which mostly restates the schema's nullable default. The description does not clarify whether gateway_id takes an ID or a name, nor what happens to the result set when it is omitted (all gateways vs. a default).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("List all clouds/zones configured in HPE VME") and adds a definition of what a cloud means in Morpheus, so its scope is unambiguous. It does not explicitly contrast itself with sibling listers such as vme_list_instances or list_providers, but the resource target is distinct enough that an agent can disambiguate without reading the schema.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool versus alternatives, and no prerequisites or exclusions. The only usage-like signal is the parenthetical "(optional)" next to gateway_id, which does not explain when supplying a gateway is appropriate or what the default behavior is.

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