Skip to main content
Glama

Com List Servers

com_list_servers
Read-onlyIdempotent

Lists HPE ProLiant servers managed in Compute Ops Management with health, power, iLO, OS, CPU, and firmware details, returning the full fleet in one call for tables or comparisons.

Instructions

Servers in Compute Ops Management: name, serial, model, generation, health, power, COM connection, subscription, iLO host/IP/version, OS, CPU vendor and firmware bundle. One call returns the whole fleet, so use it for any table or comparison across servers. Set include_hardware for CPU and GPU columns.

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": "com_list_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
healthNoOnly servers with this health summary.
accountNoCOM account name from list_servers; omit to use the first one.
connectedNoOnly servers whose iLO is (or isn't) connected to COM.
name_containsNoCase-insensitive substring of the server name.
include_hardwareNoAdd a `hardware` object per server: CPU model/count/cores and GPUs (name, vendor, count, health) from COM's cached inventory. Slower (one read per server, done inside this call); use it for tables with CPU or GPU columns instead of calling com_get_server per server.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior. The description adds real operational context beyond them: one call returns the entire fleet, and include_hardware triggers one read per server inside the call, making it slower. That latency/fan-out disclosure is exactly the kind of thing annotations cannot express.

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?

Front-loaded with the resource and returned fields, then usage, then the one parameter worth calling out. Dense and free of filler, though the long field roster in sentence one could be trimmed given an output schema exists.

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?

With an output schema present, return values need no further explanation, and annotations cover safety. The description still supplies the batch-vs-per-server cost tradeoff and the fleet-wide scope, leaving little an agent would need before invoking it 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%, so every parameter is already documented. The description only echoes include_hardware's purpose, adding no filter semantics (health, account, connected, name_contains) beyond the schema and no syntax or format details, so the baseline of 3 applies.

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?

States a specific verb and resource ('Servers in Compute Ops Management') and enumerates the dimensions returned (health, power, COM connection, iLO, OS, CPU/firmware), so an agent immediately knows the payload shape. It also names the per-server alternative 'com_get_server' for the hardware case, which distinguishes it from a single-server read.

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?

'use it for any table or comparison across servers' gives a clear when-to-use rule, and 'instead of calling com_get_server per server' names an alternative and the condition that selects this tool. No explicit when-not-to-use beyond that one case, so it falls short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.