Skip to main content
Glama

Resume monitor

resume_monitor

Resume a paused website monitor by UUID to restore change tracking; requires a write-scope API key and stays within the plan's active-monitor limit.

Instructions

Resume a paused monitor (requires a write-scope API key; subject to the plan's active-monitor limit).

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": {
      "uuid": "<uuid>"
    },
    "name": "resume_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does contribute two real behavioral facts: a write-scope API key is required and the action is bounded by the plan's active-monitor limit. It omits what happens on failure (e.g., monitor not paused, quota exceeded) and whether the call is idempotent or what it returns.

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?

One sentence, front-loaded with the action and its precondition, with the auth and quota caveats parenthetically appended. No filler or redundancy.

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 state-change tool with no output schema, the definition covers the key operational constraints (permission scope and quota). The remaining gap is error/edge-case behavior for monitors that are not in a paused state.

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 a single parameter and schema description coverage is 100% — the schema already explains that 'uuid' comes from list_monitors. The description adds no additional parameter meaning, which is acceptable at this baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Resume a paused monitor') and adds a state precondition ('paused'), which makes it distinguishable from the inverse pause_monitor sibling. It stops short of naming that counterpart explicitly, so it is clear but not maximally differentiating.

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?

Usage is implied rather than stated: the tool applies to monitors that are already paused, and the agent must hold a write-scope API key. There is no explicit 'use this instead of X' guidance and no statement of what to do if the monitor is not currently paused.

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