Skip to main content
Glama

Delete a monitor

delete_monitor
DestructiveIdempotent

Deletes a monitor and its history. Frees its plan slot.

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

Input Schema

NameRequiredDescriptionDefault
idYesMonitor ID from list_monitors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real value by disclosing that monitor history is destroyed and that a plan slot is freed — two consequences not visible in the structured fields. It stops short of stating permissions or confirmability.

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, zero filler, the destructive scope front-loaded before the side effect. Nothing could be removed without losing 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 destructive tool with no output schema, the description covers the essential outcome and the side effect on plan quota. Minor gaps remain around what happens to dependent artifacts (alerts, notifications) and required permissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter, fully described in the schema (uuid, 'Monitor ID from list_monitors'), so the description needn't compensate. It adds no meaning beyond the schema, but the baseline for a fully-covered single param is 4.

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?

Specific verb+resource: 'Deletes a monitor and its history' clearly states the operation and its scope, which is more than a bare 'delete'. It does not explicitly distinguish itself from siblings like pause_monitor or update_monitor, so it falls short of a 5.

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?

'Frees its plan slot' implies a use case (permanent removal to reclaim quota), but the description never states when to prefer this over pause_monitor or resume_monitor, nor any exclusions. Usage is inferable but not spelled out for a destructive operation.

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