Skip to main content
Glama

Pause monitor

pause_monitor

Stop scheduled checks for a monitor while preserving its check history. Requires a write-scope API key.

Instructions

Pause a monitor — stops scheduled checks, keeps history (requires a write-scope API key).

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": "pause_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and usefully discloses that scheduled checks stop, history is retained, and a write-scope API key is required. It does not describe the effect on in-flight checks or whether repeated calls are idempotent, but it covers the primary behavioral and authorization concerns.

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 a single front-loaded sentence with no wasted wording. The key behavior and authorization constraint are both stated compactly.

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 tool with no output schema, the description is nearly complete: it explains what changes, what is preserved, and the API key requirement. Minor details such as the effect on currently running checks are omitted but not essential for correct invocation.

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?

The single uuid parameter is fully documented in the schema as coming from list_monitors. The description adds no additional parameter guidance, which is acceptable given 100% schema description coverage.

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 states a specific verb and resource: pause a monitor. It also distinguishes the outcome from deletion by noting that history is kept, though it does not explicitly contrast with resume_monitor or other siblings.

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?

The description implies the tool is for temporarily stopping scheduled checks while retaining history, which gives useful usage context. However, it does not explicitly state when to use pause_monitor versus alternatives such as delete_monitor or resume_monitor, nor does it provide exclusions.

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