Skip to main content
Glama

Oneview Get Server Hardware

oneview_get_server_hardware
Read-onlyIdempotent

Retrieve detailed HPE OneView server hardware data, including UID light state, firmware components with locations and versions, and active alerts, to inspect and troubleshoot a specific server.

Instructions

One OneView server in detail: the list fields plus UID light, every firmware component with location and version, and its active alerts.

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

Input Schema

NameRequiredDescriptionDefault
serverYesServer hardware name (e.g. 'Enclosure-01, bay 2'), OS hostname, serial, UUID or iLO IP.
applianceNoOneView appliance 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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds that the payload spans list fields plus UID light, firmware components and active alerts, but this is essentially a preview of return content that the output schema already defines, and it says nothing about authentication, appliance scoping behavior, or failure modes for an unknown server.

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?

A single front-loaded sentence that identifies the subject and enumerates the distinguishing payload contents with no filler. It is slightly dense as a noun phrase rather than a clause, but every element 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 only two fully documented parameters, full annotations and an output schema, the description needs only to establish scope and it does so. The remaining gap is routing guidance against the sibling list/get tools, which is a usage rather than a completeness issue.

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%, with the server parameter explicitly accepting name, hostname, serial, UUID or iLO IP, and appliance defaulting to the first appliance. The description adds no further parameter meaning, so the baseline of 3 applies when the schema does all the work.

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?

States a specific verb and resource: retrieve one OneView server hardware record in detail, enumerating the extra content (UID light, firmware components with location/version, active alerts). The phrase 'the list fields plus' implicitly contrasts it with the list sibling, so an agent can tell it returns detail for a single server rather than a collection.

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?

Usage is only implied: 'in detail' suggests this is the drill-down after a list call, and the sibling oneview_list_server_hardware is never named as the alternative. There is no explicit when-to-use or when-not-to-use guidance, and no stated prerequisite (e.g. that the server must first be discovered).

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