Skip to main content
Glama

Oneview List Alerts

oneview_list_alerts
Read-onlyIdempotent

List HPE OneView alerts with affected resource, description, and corrective action; filter by severity, appliance, and active status to identify current server issues.

Instructions

Newest OneView alerts with the affected resource, description and corrective action.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
severityNoOnly this severity.
applianceNoOneView appliance name from list_servers; omit to use the first one.
active_onlyNoOnly alerts that are still Active.

Output Schema

NameRequiredDescriptionDefault
resultYes

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 this a read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds only the 'Newest' ordering hint and the returned field set, without saying whether results span all appliances, how truncation at the default limit of 50 behaves, or that active_only defaults to true.

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 with zero filler, but it is arguably too terse for a tool with four filtering parameters and an implicit multi-appliance scope.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. What is missing is the cross-appliance scope and default appliance behavior, which matter for an open-world listing tool with an appliance selector.

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?

With four parameters and 75% schema description coverage, the schema already documents severity, appliance, and active_only including defaults. The description adds no filtering semantics or format details beyond what the schema states, so the baseline of 3 applies.

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 names a specific resource (OneView alerts) and the fields each alert carries (affected resource, description, corrective action), so an agent knows what it will get back. It does not distinguish this from the sibling com_list_alerts, which likely covers a different management plane, leaving ambiguity about which alert source to pick.

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 exclusion of alternatives such as com_list_alerts, and no mention that the appliance parameter defaults to the first appliance when omitted. The agent must infer call conditions entirely from the schema.

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