Monitoring AIops

mute_alerts

Destructive

Temporarily suppress alerts for a monitored entity for a set number of minutes, reducing noise during maintenance or known events.

Instructions

[WRITE][risk=medium] Time-boxed alert suppression for an entity. Inverse: unmute_alerts.

Args: entity_uri: SWIS entity URI to suppress (e.g. from list_muted / SWQL). minutes: Suppression window length in minutes. target: SolarWinds target name from config; omit for the default.

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": {
      "entity_uri": "<entity_uri>"
    },
    "name": "mute_alerts"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No
`minutes`	No
`entity_uri`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Sep 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false. The description adds real value on top: it flags the operation as a time-boxed (self-expiring) suppression and points to the inverse operation, which conveys reversibility and scope beyond the annotation flags.

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?

Front-loaded with the [WRITE][risk=medium] tag and a one-line purpose, followed by a compact Args block. No sentence is wasted and the most selection-relevant information comes first.

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?

For a destructive write tool with no output schema and no annotation coverage of duration/expiry semantics, the description supplies purpose, risk tag, time-boxing, inverse operation, and per-parameter meaning. It stops short of stating permission requirements or what the call returns, but what is present is sufficient to invoke correctly.

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 description coverage is 0%, so the description carries the burden and does so for all three params: entity_uri is defined as a SWIS URI with a sourcing hint (list_muted/SWQL), minutes as a window length, and target as a config name with 'omit for the default'. It does not restate the schema defaults (minutes=60), a minor omission.

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?

States a specific verb and resource: 'Time-boxed alert suppression for an entity.' It also names the inverse tool (unmute_alerts), letting an agent place it correctly relative to its one obvious counterpart without opening a schema.

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 'Time-boxed' qualifier and the named inverse imply the intended scenario (temporary suppression that can be reversed), but there is no explicit when-to-use vs when-not guidance, nor reference to list_muted or schedule_maintenance as alternatives for longer suppression.

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