Skip to main content
Glama

Com List Alerts

com_list_alerts
Read-onlyIdempotent

Retrieve recent HPE ProLiant COM alerts for hardware, security, and service events, filtering by server, severity, or account; uncleared alerts are returned by default.

Instructions

Newest COM alerts (hardware, security, service events), uncleared only by default.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
serverNoOnly alerts for this server (name, serial, iLO IP or id).
accountNoCOM account name from list_servers; omit to use the first one.
severityNoOnly this severity.
include_clearedNoAlso return alerts that have cleared.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new context beyond them: results are ordered newest-first, filtered to three event categories, and cleared alerts are excluded unless opted in. It stops short of stating pagination behavior against the limit maximum or how the account default is resolved across multiple COM accounts.

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?

A single front-loaded sentence with no filler. Ordering, category scope, and the default filter are all packed into one clause, and nothing is repeated from the schema or name.

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 values need not be described, and the annotations carry the safety profile. With 80% schema coverage and rich annotations, the definition is nearly sufficient; the remaining gap is the absence of routing guidance versus oneview_list_alerts and clarification of multi-account default behavior.

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 80%, so the schema already documents server, account, severity and include_cleared individually. The only added meaning is the tool-level statement that uncleared-only is the default, which reinforces include_cleared; limit and its 1000 maximum receive no interpretation in the description.

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 (COM alerts) with a clear scope: newest first, restricted to hardware/security/service event categories, and uncleared-only by default. That is more specific than a bare 'list alerts', though it never explains how COM alerts differ from the sibling oneview_list_alerts, leaving the agent to infer selection from the name prefix alone.

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 explicit when-to-use guidance and no named alternative. 'Uncleared only by default' hints at the default behavior but does not tell the agent when to prefer this tool over oneview_list_alerts or when to set include_cleared, so the caller must derive usage from the schema defaults.

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