Skip to main content
Glama
vmware-skills

vmware-aria

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_alerts

Read-onlyIdempotent

Retrieve alert summaries from Aria Operations with filters for criticality, resource, and active status. Paginate through results to get names, impact, timestamps, and control state.

Instructions

[READ] List alerts from Aria Operations.

Returns alert summaries: name, criticality, status, impact, resource_id, resource_name, resource_kind, timestamps (start/update *_time_ms, and start_time_utc / update_time_utc in ISO-8601 UTC), and control state. resource_name and resource_kind are resolved in one batched lookup per page; they are null when that failed, the resource no longer exists, or Aria holds no name for it, and the envelope's resource_names_note (null when every name resolved) then says which — null means unknown, not "no resource".

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.1/5.0
Behavior5/5

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

The annotations already mark the tool as read-only, open-world, idempotent, and non-destructive, and the description's '[READ]' tag aligns with them. The description adds substantial behavioral context beyond the annotations: batched resource-name resolution, null semantics ('null means unknown, not "no resource"'), the meaning of truncated, and the rejection of out-of-range limit values. No contradiction exists.

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?

Despite being long, the description is dense and efficient. It front-loads the core purpose, then covers return fields and pagination semantics without redundant statements. Every sentence contributes operational or semantic value, and the structure flows logically from summary to envelope to paging instructions.

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 fully carries the burden of explaining the return envelope (items, returned, limit, total, truncated, hint, next_offset) and edge cases like null resource names and null totals. It also gives explicit instructions for correct pagination and warns against looping on truncated, making the tool safe and complete for an agent to use.

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%, so every parameter is already documented in the input schema. The description largely restates the schema's parameter semantics, such as limit's 1–500 range and offset's 'how many rows to skip', without adding significant new parameter-specific meaning. Baseline 3 is appropriate.

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 '[READ] List alerts from Aria Operations', a specific verb and resource, and clearly enumerates the returned alert summaries. It is clear and unambiguous, but it does not explicitly name or differentiate any sibling tools such as get_alert or list_alert_definitions, so it stops short of 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 Guidelines3/5

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

The description provides rich operational guidance on how to page through results—'pass it back as offset and stop when it is null' and 'Do not loop on truncated'. However, it gives no explicit when-to-use guidance or alternative routing, leaving the choice between list_alerts and sibling list/detail tools to be inferred.

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

Deploy Server

Other Tools