Skip to main content
Glama

Resume a monitor

resume_monitor
Idempotent

Starts checking a paused monitor again. 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": "resume_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely new behavioral fact — "Free" (no billing impact) — but omits what happens on a non-paused monitor and whether checks fire immediately or on the next interval.

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?

Two short sentences with zero padding and the action front-loaded; the cost note is placed last where it does not obstruct. The one-word fragment "Free." is terser than ideal but does carry real information.

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 one-parameter state-toggle with full annotation coverage and no output schema, the definition says enough to call it correctly. The main remaining gap is the error/precondition case for a monitor that was never paused.

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 coverage is 100% and the single parameter is documented as "Monitor ID from list_monitors," which even points at the discovery path. The description adds nothing about the id beyond the schema, so baseline 3 applies.

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?

"Starts checking a paused monitor again" gives a specific verb (resume/start checking) and a specific resource state (a paused monitor), which is enough to tell it apart from pause_monitor and get_monitor by inference. It does not explicitly name the inverse sibling, so differentiation relies on the reader's reasoning rather than being stated.

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 phrase "a paused monitor" implicitly scopes usage to monitors already in the paused state, which is useful context. However, it never states when to use this versus pause_monitor or update_monitor, nor what to do if the monitor is not paused.

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