vmware-aria

create_alert_definition

Create a monitoring alert definition in Aria Operations from existing symptom definitions. Specify resource kind and symptom IDs to define when the alert should fire.

Instructions

[WRITE] Create a new alert definition referencing existing symptom definitions.

Returns the new definition's id and name. Run list_symptom_definitions first for symptom_definition_ids; to silence an existing definition use set_alert_definition_state rather than creating a variant.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "description": "<description>",
      "resource_kind": "<resource_kind>",
      "symptom_definition_ids": "<symptom_definition_ids>"
    },
    "name": "create_alert_definition"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Alert definition name (must be unique in Aria Operations).
`target`	No	Aria target name from config; default when omitted.
`criticality`	No	Alert severity: INFORMATION, WARNING, IMMEDIATE, CRITICAL.	WARNING
`description`	Yes	When and why this alert fires.
`adapter_kind`	No	Adapter kind key. Default VMWARE (vSphere adapter).	VMWARE
`resource_kind`	Yes	VirtualMachine, HostSystem, ClusterComputeResource, or Datastore.
`symptom_definition_ids`	Yes	Symptom definition UUIDs; any one firing triggers the alert (OR).

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.10.0Sep 8, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / adapter_kind / description

Added value: +"Adapter kind key. Default VMWARE (vSphere adapter)."

addedInput schema / properties / criticality / description

Added value: +"Alert severity: INFORMATION, WARNING, IMMEDIATE, CRITICAL."

addedInput schema / properties / description / description
```
Added value: +"When and why this alert fires."
```

addedInput schema / properties / name / description

Added value: +"Alert definition name (must be unique in Aria Operations)."

addedInput schema / properties / resource_kind / description

Added value: +"VirtualMachine, HostSystem, ClusterComputeResource, or Datastore."

addedInput schema / properties / symptom_definition_ids / description

Added value: +"Symptom definition UUIDs; any one firing triggers the alert (OR)."

addedInput schema / properties / target / description

Added value: +"Aria target name from config; default when omitted."

Addedv1.5.29May 29, 2026
Removedv1.5.28May 21, 2026
Addedv1.5.18May 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish that this is a write operation, non-idempotent, and non-destructive. The description adds useful behavioral context by stating the return value ('Returns the new definition's id and name') and by requiring that symptom definitions already exist before calling.

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?

Three tightly packed sentences with no filler. The main purpose is first, followed by return value, then prerequisite and alternative routing. Every sentence contributes to correct tool selection or invocation.

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?

For a 7-parameter create operation with no output schema, the description covers the essential missing context: what it creates, what it returns, what must be done beforehand, and which sibling to use instead. The remaining parameter details are fully covered by the schema.

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

Parameters4/5

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

Schema coverage is 100%, so all parameters are already described. The description adds practical value beyond the schema by telling the agent to call list_symptom_definitions first for symptom_definition_ids, which directly informs how to populate a required parameter.

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: 'Create a new alert definition referencing existing symptom definitions.' It clearly distinguishes this from the sibling set_alert_definition_state by explicitly warning not to create a variant just to silence an alert.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: run list_symptom_definitions first to obtain valid symptom_definition_ids, and use set_alert_definition_state instead when the goal is to silence an existing definition. This is actionable and prevents misuse.

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

Deploy Server