Skip to main content
Glama
Sign In
Maintenant

Maintenant

by kOlapsis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

resume_monitor

Resumes a paused heartbeat monitor to restart monitoring checks. Supports heartbeat monitors only.

Instructions

Resume a paused heartbeat monitor. Only heartbeat monitors are supported.

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

Input Schema

NameRequiredDescriptionDefault
monitor_idYesMonitor ID to resume
monitor_typeYesType of monitor, only heartbeat is supported

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It reveals the state transition (paused to active) but says nothing about whether the call is idempotent, what happens if the monitor is not currently paused, what permissions or paid-tier gating may apply, or what is returned.

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?

Two short sentences with zero filler, and the core action is front-loaded before the scope caveat.

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?

For a simple two-parameter state-changing tool with a fully documented schema and no output schema, the description covers what the tool does and its type restriction. However, with zero annotation coverage it should have addressed the failure modes and side effects of a mutation that an agent needs before invoking it.

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 description coverage is 100%, so both monitor_id and monitor_type are already documented, including the heartbeat-only constraint. The description repeats that constraint but adds no new meaning such as ID format or accepted values beyond heartbeat.

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 uses a specific verb and resource ("Resume a paused heartbeat monitor") and adds a scope constraint ("Only heartbeat monitors are supported"). It does not explicitly name the sibling it pairs with (pause_monitor), so an agent gets a clear purpose but must infer the partner tool.

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?

"Resume a paused" establishes the precondition for use, and "Only heartbeat monitors are supported" is an explicit exclusion. It is weaker on alternatives – it never points to pause_monitor as the inverse operation or says what to do for non-heartbeat monitor types.

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

Deploy Server

Other Tools