Skip to main content
Glama

Pause a monitor

pause_monitor
Idempotent

Stops checking a monitor. Free.

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": {
      "id": "<id>"
    },
    "name": "pause_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the essential safety profile is covered and the description adds only the word "Free", which does convey that pausing incurs no billing cost. Beyond that it says nothing about state retention, whether checks resume automatically, or what happens to in-flight alerts.

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?

Extremely short and front-loaded, with no filler sentences. However, the fragment "Free." reads as a stray afterthought without context about what is free (cost? quota?), so brevity edges into under-specification rather than polished concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has a fully documented single parameter, and annotations cover reversibility and safety, so the core is adequate. Still missing is the key operational fact an agent needs: that the monitor is retained and can be reactivated via resume_monitor, versus being removed.

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 required id parameter with 100% schema description coverage, including format uuid and a pointer to list_monitors, so the schema fully carries parameter semantics. The description adds nothing about the identifier beyond what is already structured, which is the expected baseline for this coverage level.

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

Purpose3/5

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

"Stops checking a monitor" names a resource and an action, but the verb is ambiguous: 'stops' could plausibly mean delete or disable, and the sibling set contains delete_monitor and resume_monitor that need distinguishing. A reader can guess it means pause, but the description never uses that word or clarifies that configuration is retained.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance at all. There is no mention of the obvious alternative (delete_monitor for permanent removal) or of resume_monitor as the inverse operation, leaving the agent to infer the distinction from sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources