Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Remote

list_alerts

Read-onlyIdempotent

Retrieve active alerts from Aria Operations with filters for criticality and resource, plus pagination controls. See alert name, status, impact, and timestamps to prioritize response.

Instructions

[READ] List alerts from Aria Operations.

Returns alert summaries: name, criticality, status, impact, resource_id, timestamps, and control state. The Alert model does not carry a resource name — resolve it via get_resource(resource_id).

Returns a paginated envelope: items, returned, limit, total (null when the API reports no size), truncated, hint, next_offset. Check truncated before calling this the complete set.

Page it: limit is the page size (1-500; 0, negatives and anything above 500 are rejected, not clamped), offset is how many rows to skip, and next_offset is the offset of the next page — pass it back as offset and stop when it is null. Do not loop on truncated: that says this page is not the whole collection, so it stays true on the last page of a walk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, 1–500 (default 100). Out-of-range is rejected.
offsetNoAlerts to skip; pass the previous response's next_offset.
targetNoAria target name from config; default when omitted.
active_onlyNoReturn only active (non-cancelled) alerts. Default True.
criticalityNoFilter by criticality: INFORMATION, WARNING, IMMEDIATE, CRITICAL.
resource_idNoScope alerts to a specific resource UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.10.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / active_only / description
      Added value: +"Return only active (non-cancelled) alerts. Default True."
    • addedInput schema / properties / criticality / description
      Added value: +"Filter by criticality: INFORMATION, WARNING, IMMEDIATE, CRITICAL."
    • addedInput schema / properties / limit / description
      Added value: +"Page size, 1–500 (default 100). Out-of-range is rejected."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Alerts to skip; pass the previous response's next_offset.",
+  "title": "Offset",
+  "type": "integer"
+}
    • addedInput schema / properties / resource_id / description
      Added value: +"Scope alerts to a specific resource UUID."
    • addedInput schema / properties / target / description
      Added value: +"Aria target name from config; default when omitted."
  2. Changed1 schema field changedv1.8.9
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "list_alertsOutput",
-  "type": "object"
-}New value: +null
  3. Addedv1.5.29
  4. Removedv1.5.28
  5. First observedv1.3.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and open-world. The description goes well beyond that by documenting pagination semantics, the exact meaning of truncated, the behavior of next_offset (pass back and stop when null), and the warning not to loop on truncated. It also reveals that the Alert model lacks a resource name, which is critical behavioral context.

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?

Every sentence adds value. The description is structured with a one-line purpose, a return-format summary, and a dedicated pagination walk-through. It is detailed without redundancy, and the most important caveats are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must explain the response shape and pagination protocol, and it does so thoroughly. It covers the envelope fields, the truncated trap, and the cross-reference to get_resource. For a list operation with six optional parameters, this is complete enough for an agent to call and page correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds essential parameter behavior: limit is rejected (not clamped) outside 1-500, offset is an absolute skip count, next_offset must be passed back as offset, and the walk stops on null. This is practical, non-obvious semantics that the schema alone does not convey.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'List alerts from Aria Operations.' It clearly distinguishes list_alerts from siblings like list_alert_definitions, get_alert, and investigate_alert by focusing on alert summaries rather than definitions or single-alert lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly scopes the tool's use case and even directs follow-up resource-name resolution via get_resource. It does not explicitly enumerate when not to use this tool, but the purpose is distinctive enough among siblings and the 'List alerts' phrasing makes the intended context unmistakable.

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

Install Server

Other Tools