UptyBots

Resume monitor

resume_monitor

Idempotent

Start checking a paused monitor again, with the configuration it had before. The first check runs immediately rather than after the usual interval, so the current state is known within moments. Safe to call on a monitor that is already running.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Monitor id to resume, as returned by list_monitors.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Monitor id, used by every other tool.
`url`	No
`name`	No
`type`	No
`isActive`	No	False while the monitor is paused.
`frequency`	No	Check interval in minutes.
`statusSummary`	No	Current state, for example GOOD or ERROR.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedAug 20, 2026

changedInput schema / properties / id / description

Previous value: -"Monitor ID to resume"New value: +"Monitor id to resume, as returned by list_monitors."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "frequency": {
+      "description": "Check interval in minutes.",
+      "type": "integer"
+    },
+    "id": {
+      "description": "Monitor id, used by every other tool.",
+      "type": "integer"
+    },
+    "isActive": {
+      "description": "False while the monitor is paused.",
+      "type": "boolean"
+    },
+    "name": {
+      "type": "string"
+    },
+    "statusSummary": {
+      "description": "Current state, for example GOOD or ERROR.",
+      "type": "string"
+    },
+    "type": {
+      "enum": [
+        "PING",
+        "HTTP",
+        "API",
+        "SSL",
+        "DOMAIN",
+        "PORT"
+      ],
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}

First observedAug 20, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds transparency beyond annotations by noting immediate check and safe on running monitor, consistent with idempotent and non-destructive hints.

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 concise sentences with no redundancy. Clear and well-structured.

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?

Covers the effect, immediate behavior, and safety. Does not mention error scenarios, but that's not critical for this simple operation.

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?

Schema already fully describes the id parameter. Description adds no extra parameter details, so baseline score is appropriate.

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?

Clearly states the action: resumes a paused monitor and specifies immediate first check. Distinguishes from pause_monitor (sibling) implicitly.

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 guidance on safety when already running, but does not explicitly compare with alternatives or state when not to use. Still clear enough.

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

All UptyBots tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose. The six monitor creation tools are explicitly differentiated in their descriptions (e.g., HTTP vs API vs SSL vs domain), and lifecycle tools like delete, pause, resume, and list are unambiguous. Overlap is minimal and explicitly addressed.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (e.g., create_http_monitor, get_stats_hourly, pause_monitor). No mixed conventions or vague verbs; the pattern is uniform and predictable.

Tool Count4/5

15 tools is on the higher end of the ideal range, but each tool earns its place. The count reflects a comprehensive monitoring surface without unnecessary redundancy. Slightly over the typical sweet spot, but justified by the domain.

Completeness4/5

The tool surface covers creation, deletion, pause/resume, listing, retrieval, incident history, and two levels of statistics, plus notifications. A notable gap is the absence of an update/edit tool for existing monitors, which agents may need to adjust configurations. Otherwise, the lifecycle is well covered.

Resources

Need Help?