PingRelay MCP Server

monitor_resume

Idempotent

Clear a non-deleted monitor's paused flag in the authenticated organization. An already resumed monitor succeeds without toggling its state. Does not enable a disabled monitor or remove maintenance windows.

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": {
      "monitorExternalId": "<monitorExternalId>"
    },
    "name": "monitor_resume"
  }
}

Input Schema

Name	Required	Description	Default
`monitorExternalId`	Yes	External monitor GUID returned as Id by MonitorList or MonitorListRecent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026
- addedInput schema / properties / monitorExternalId / description
```
Added value: +"External monitor GUID returned as Id by MonitorList or MonitorListRecent."
```
First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare idempotency, non-destructiveness, and that this is not a read-only operation. The description adds useful boundaries beyond the annotations: only the paused flag is cleared, disabled monitors are not enabled, and maintenance windows are unaffected.

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?

The description is three tightly written sentences with no waste. The primary action and scope are front-loaded, followed by important behavioral boundaries.

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 simple one-parameter mutation with annotations covering idempotency and safety, the description supplies enough scope and edge-case behavior. It does not describe return values or error behavior for invalid/deleted monitor IDs, but no output schema exists and the core invocation context is clear.

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?

There is one required parameter, and the schema has 100% description coverage defining it as an external monitor GUID returned by MonitorList or MonitorListRecent. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: clearing a monitor's paused flag. It adds scope (authenticated organization) and clearly separates the operation from related actions such as enabling a disabled monitor or removing maintenance windows.

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?

The description gives clear conditions for use: the monitor must be non-deleted, and already-resumed monitors are safe. It also states when-not conditions around disabled monitors and maintenance windows, though it does not explicitly name monitor_pause as the counterpart tool.

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

All PingRelay MCP Server tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?