Monitoring AIops

unmanage_node

Destructive

Temporarily mask monitoring for a SolarWinds Orion node by setting a start and required end time, with dry-run preview and reversible remanage.

Instructions

[WRITE][risk=high] Unmanage a node — masks its monitoring. Inverse: remanage_node.

Pass dry_run=True to preview. Reversible → remanage. An end time is required (no open-ended unmanage).

Args: node_id: Numeric Orion NodeID. start_iso: Unmanage window start (ISO-8601 UTC timestamp). end_iso: Unmanage window end (ISO-8601 UTC timestamp) — required. dry_run: If True, preview without unmanaging. 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": {
      "node_id": "<node_id>",
      "start_iso": "<start_iso>",
      "end_iso": "<end_iso>"
    },
    "name": "unmanage_node"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No
`dry_run`	No
`end_iso`	Yes
`node_id`	Yes
`start_iso`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Sep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare write/destructive/non-idempotent, but the description adds real substance: it discloses the actual effect (monitoring masked, not deleted), that the action is reversible via remanage_node, the dry_run preview path, and the mandatory end time. It stops short of mentioning permissions or the masking scope limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the [WRITE][risk=high] flag, then effect and inverse, then args — good structure. Minor redundancy: the dry_run preview is stated twice (once in prose, once in Args) and the remanage inverse is stated twice, but overall it is tight.

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 high-risk write with no output schema, it covers purpose, reversibility, dry_run, required parameters and timestamp format, which is what an agent needs to call it correctly. It omits auth/permission requirements and any note on output or confirmation behavior, a minor gap.

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?

Schema description coverage is 0%, so the description carries the full burden and does: node_id (Numeric Orion NodeID), start_iso/end_iso (ISO-8601 UTC, end required), dry_run (preview), and target (config target name, omit for default). Nothing essential is left undocumented.

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 ('Unmanage a node') and immediately clarifies the effect ('masks its monitoring'). It explicitly names its inverse (remanage_node), letting an agent place it against siblings like remove_node and schedule_maintenance 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 Guidelines4/5

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

Provides actionable guidance ('Pass dry_run=True to preview', 'Reversible → remanage', 'no open-ended unmanage') and names the inverse tool. However it never contrasts with scheduling siblings like schedule_maintenance or remove_node, so the agent must infer when this is preferred over those.

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