Skip to main content
Glama

vme_list_servers

List all physical hosts managed by HPE VME with CPU, memory, and status, and filter results by cloud/zone or gateway to inspect fleet inventory.

Instructions

List all physical hosts managed by HPE VME with CPU, memory and status.

Args: cloud: Filter by cloud/zone name (optional). 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_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudNo
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it implies a read-only enumeration and discloses that returned entries include CPU, memory, and status. However, it does not cover permissions, pagination, result limits, or error behavior, and 'List all' leaves enumeration completeness ambiguous.

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 description is short and front-loaded, with the core action stated first and the optional arguments listed afterward. The Args block is standard and there is little wasted wording.

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

Completeness4/5

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

For a simple two-parameter read-only listing tool with no output schema, the description is mostly complete: it states the resource, output fields, and both optional filters. Minor gaps around pagination and the interaction between cloud and gateway filters keep it from being fully complete.

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 description coverage is 0%, so the description must explain the parameters, and it does: cloud filters by cloud/zone name, and gateway_id targets a gateway, both optional. The explanations add useful meaning, though gateway targeting and filter interaction remain somewhat vague.

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 states a specific verb and resource: list physical hosts managed by HPE VME, and adds that CPU, memory, and status are included. It implicitly distinguishes physical hosts from sibling instance/cloud listings, but it does not explicitly name or route against alternatives.

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

Usage Guidelines3/5

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

The 'list all' framing plus optional cloud and gateway filters implies when the tool is useful, but there is no explicit guidance on when to use it instead of vme_list_instances or vsphere_list_hosts. No exclusions or prerequisites are stated.

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