Skip to main content
Glama

Oneview List Server Hardware

oneview_list_server_hardware
Read-onlyIdempotent

Retrieve HPE OneView-managed server hardware details, including model, serial, status, power, CPU, memory, OS, and iLO firmware/IP, to audit or troubleshoot infrastructure.

Instructions

Servers managed by OneView: name, OS hostname, model, serial, status, power, assigned profile, enclosure/bay, CPU, memory, ROM, OS and iLO (model, firmware, IP).

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

Input Schema

NameRequiredDescriptionDefault
applianceNoOneView appliance name from list_servers; omit to use the first one.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds the returned field inventory, which is useful context, but says nothing about scope (one appliance vs all), pagination, or result size for a potentially large fleet listing.

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

Conciseness3/5

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

It is a single sentence with no filler, but it is structured as a raw field dump with an awkward nested parenthetical for iLO. The resource is front-loaded, yet a leading verb and scope statement would earn the space better.

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?

With an output schema present, the description needn't explain return values, and the annotations carry the safety profile. However, for a fleet-wide listing tool it omits the appliance scoping behavior and any sense of how results are bounded, leaving a moderate gap.

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 the single optional 'appliance' parameter is fully documented in the schema, so the baseline of 3 applies. The description does not mention the appliance scoping at all, adding no meaning beyond the schema.

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

Purpose3/5

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

The description is a noun phrase enumerating returned attributes rather than a verb+resource statement, so the 'list' action is only implied by the name. An agent can infer it retrieves server records, but nothing distinguishes it from siblings like oneview_get_server_hardware, com_list_servers, or list_servers.

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 when-to-use guidance, no prerequisites, and no mention of when a single-server getter or a different server-list tool would be preferable. The only actionable hint, the appliance parameter, lives in the schema rather than the description.

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