Skip to main content
Glama

Oneview Get Appliance

oneview_get_appliance
Read-onlyIdempotent

Retrieve an HPE OneView appliance health and inventory report covering model and software version, CPU/memory/disk status, resource counts, power state, and active alerts by severity.

Instructions

OneView appliance report: model and software version, appliance CPU/memory/disk health, counts of server hardware, profiles, enclosures and interconnects, server hardware by status and power, and active alerts by severity.

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

Input Schema

NameRequiredDescriptionDefault
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

B3.2/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 useful content scope by enumerating what the report aggregates, but says nothing about cost of the call, whether the aggregate queries multiple endpoints, or how stale the health data might be. With annotations carrying the safety burden, this is an adequate but not rich addition.

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?

One sentence, front-loaded with the tool's identity before the content list, with zero filler. The enumeration is long but each item is a distinct data category rather than padding. Slightly dense as a single run-on, which keeps it from a 5.

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, so return-value documentation is not required of the description, and the description still previews the report's sections. Combined with full annotation coverage and a fully documented single parameter, an agent has enough to invoke this correctly. Only the lack of routing guidance against the many list_* siblings keeps it below 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 description coverage is 100% and the single 'appliance' parameter is documented in the schema, including the 'omit to use the first one' default behavior. The description adds no meaning beyond that. Baseline 3 applies when the schema fully carries parameter semantics.

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?

The description opens with a specific verb+resource pairing ('OneView appliance report') and enumerates the exact contents: model/software version, CPU/memory/disk health, hardware/profile/enclosure/interconnect counts, hardware by status and power, and alerts by severity. That makes it clearly distinguishable from the granular siblings like oneview_list_server_hardware or oneview_list_alerts. It stops short of naming a sibling alternative, so it is not a 5.

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 or when-not-to-use guidance in the description. It never says to prefer this over oneview_list_alerts or oneview_get_server_hardware when the agent only wants one slice of the data, nor does it state prerequisites such as needing a valid OneView connection. The only scoping hint ('omit to use the first one') lives in the schema, not the description.

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