Skip to main content
Glama

Com Get Server

com_get_server
Read-onlyIdempotent

Retrieve detailed health, identity, firmware, CPU/GPU, iLO, subscription, and alert data for one HPE ProLiant COM server; use server lists for multiple servers.

Instructions

One COM server in detail: identity, per-subsystem health, iLO, subscription, last firmware update, full firmware inventory, CPU and GPUs (with GPU serial numbers), and its active alerts. For several servers use com_list_servers or com_list_gpus, not one call each.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "com_get_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYesCOM server name, serial number, iLO IP/hostname or id.
accountNoCOM account name from list_servers; omit to use the first one.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful scope about the breadth of the returned snapshot, but says nothing about failure modes (unknown/ambiguous server name, missing iLO), latency on a large inventory, or account-selection behavior. With annotations carrying the behavioral load, a 3 is appropriate.

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

Conciseness5/5

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

Two sentences, zero waste: the resource and its contents come first, the sibling routing second. The enumerated payload list is dense but each item conveys real scope.

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?

An output schema exists and annotations are rich, so the description needn't explain return structure, and it covers the one-vs-many usage question well. It stops short of noting edge behavior such as an unresolvable server identifier or which account is chosen when multiple exist, which keeps it from a 5.

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% and both parameters (server identifier forms, optional account defaulting to the first) are fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 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 ('One COM server in detail') and enumerates the payload: identity, per-subsystem health, iLO, subscription, firmware update and inventory, CPU/GPUs with serials, active alerts. It also names the sibling tools to use for the multi-server case, so an agent can distinguish it from com_list_servers and com_list_gpus without opening a schema.

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?

Explicitly routes the agent: use this for one server, and 'For several servers use com_list_servers or com_list_gpus, not one call each.' Both the when-to-use and the anti-pattern (per-server fan-out) are stated, leaving nothing to inference.

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