Skip to main content
Glama

Delete monitor

delete_monitor

Permanently deletes a monitor along with its checks, screenshots and HTML copies. Use only after confirming with the user, since the removal cannot be undone; pause it instead to just stop checking.

Instructions

Permanently delete a monitor with all its checks, screenshots and HTML copies (requires a write-scope API key). This cannot be undone: confirm with the user first, and use pause_monitor instead when they only want it to stop checking.

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

Input Schema

NameRequiredDescriptionDefault
uuidYesMonitor uuid (from list_monitors)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses irreversibility ("This cannot be undone"), the cascading data loss (checks, screenshots, HTML copies), and an auth requirement (write-scope API key). It does not state error behavior for a nonexistent uuid or the nature of the response, which leaves a modest gap for an unannotated mutation tool.

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 tight sentences with no filler. The destructive scope and the confirmation requirement are front-loaded before the alternative tool is mentioned.

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

Completeness5/5

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

For a destructive single-parameter tool with no annotations or output schema, the description supplies the safety profile (irreversible, cascading, write scope) and the safer alternative. Nothing essential to calling it correctly is missing.

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?

Only one parameter (uuid) and the schema documents it at 100% coverage, including its provenance ("from list_monitors"). The description adds no meaning beyond that, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Permanently delete a monitor") and immediately scopes the blast radius ("with all its checks, screenshots and HTML copies"). An agent can distinguish it from pause_monitor or update_monitor on purpose alone.

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?

Names the preferred alternative and the condition that selects it: "use pause_monitor instead when they only want it to stop checking." It also sets a precondition ("confirm with the user first"). Strong, though it does not cover edge cases such as target already deleted or not found.

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