Monitoring AIops

pause_sensor

Destructive

Temporarily pause a PRTG sensor, device, or group to stop alerts; choose indefinite or auto-resume after set minutes.

Instructions

[WRITE][risk=medium] Pause a PRTG object; reversible via resume_sensor.

Open-ended when minutes is 0, otherwise auto-resumes after minutes.

Args: object_id: PRTG object id (sensor/device/group) to pause. minutes: Auto-resume after this many minutes; 0 pauses indefinitely. message: Pause message shown in PRTG. target: Monitoring 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": {
      "object_id": "<object_id>"
    },
    "name": "pause_sensor"
  }
}

Input Schema

Name	Required	Default
`target`	No
`message`	No	paused
`minutes`	No
`object_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Sep 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare destructive=true and it tells the agent the action is reversible via resume_sensor and describes the auto-resume timing, which is genuinely useful context beyond the structured hints. It stops short of stating required permissions or what happens to in-flight alerts when pausing.

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/safety tag then a one-line purpose, followed by a tight Args block. Every line earns its place; the only minor cost is restating parameter meanings that already live in the schema titles.

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 4-parameter mutation with no output schema, the definition covers purpose, reversibility, parameter meanings, and the open-ended/auto-resume behavior. Annotations already carry the safety profile, so nothing critical is missing, though permission requirements remain unstated.

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 four parameters: object_id scope (sensor/device/group), minutes=0 semantics, message purpose, and target config override with default. This compensates well for the undocumented schema, though format details (e.g., valid target names) are absent.

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 (Pause) and resource (PRTG object/sensor) with a clear scope marker in the [WRITE][risk=medium] tag. It explicitly distinguishes itself from the resume_sensor sibling by naming it as the reversal path, so an agent can route between the two without opening schemas.

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?

It explains the key behavioral branch: minutes=0 means open-ended pause, otherwise auto-resume. It also names resume_sensor as the undo path. What's missing is explicit guidance on when to pause vs. alternatives like schedule_maintenance_prtg or mute_alerts, which overlap semantically.

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