Skip to main content
Glama

Com List Gpus

com_list_gpus
Read-onlyIdempotent

Get a GPU inventory report for an entire COM fleet: per-server GPU models, counts, health, iLO firmware, and totals by GPU model, plus flagged servers with unknown inventory.

Instructions

GPU report for the whole COM fleet in one call: per server the model, generation, iLO firmware version, health, CPU and GPUs (name, vendor, part number, count, health), plus totals by GPU model and the servers whose inventory COM does not have (their GPUs are unknown, not absent). Start here for any GPU question.

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_gpus"
  }
}

Input Schema

NameRequiredDescriptionDefault
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_servers_without_gpusNoAlso list servers with no GPU.

Output Schema

NameRequiredDescriptionDefault

No arguments

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 declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds report contents and an important interpretive caveat that servers missing from COM inventory have unknown rather than absent GPUs, which prevents a wrong conclusion from a filtered result. No pagination or scale limits are mentioned, but an output schema is present.

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 scope and payload, followed by a single short routing sentence. Density is high but every clause enumerates a distinct returned field; the parenthetical caveat earns its place.

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, the description need not explain return values, and it still summarizes them plus the one interpretive trap. For a zero-required-parameter read tool with four documented filters, this is close to complete; only scale or result-size expectations are absent.

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%, and each filter (account, connected, name_contains, include_servers_without_gpus) is already documented in the schema, including the account default. The description adds no filter semantics of its own, so the baseline applies; the inventory-missing caveat is report semantics rather than parameter semantics.

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 ('GPU report for the whole COM fleet in one call') and enumerates exactly what comes back: model, generation, iLO firmware, health, CPU, GPU details, totals by model. This is clearly distinct from the per-server siblings like com_get_server or oneview_get_server_hardware.

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?

'Start here for any GPU question' gives explicit entry-point guidance and 'in one call' implies the fleet-wide alternative to per-server queries. It does not name a specific alternative or state when-not to use it, so it stops short of the top band.

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