Skip to main content
Glama

searchnapply

Delete job monitors

monitor_delete
DestructiveIdempotent

Purpose: Delete saved monitors and everything they collected; a deletion cannot be undone. When: Only when the user asks to delete them. Cost: Under 30 tokens for the reply.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "monitorIds": [
        12
      ]
    },
    "name": "monitor_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitorIdsYesIds of the monitors to delete, 1 to 10, from monitor_list.

Output Schema

NameRequiredDescriptionDefault
failedNoIds that could not be deleted just now; present only when some could not.
deletedYesThe ids of the deleted monitors.
notFoundNoIds that name no monitor of the user; present only when some do.

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 flag destructiveHint=true and idempotentHint=true, but the description adds what the annotations cannot: that collected data is destroyed along with the monitor and that the deletion is irreversible. It says nothing about partial failures when some monitorIds are invalid, which is the main remaining behavioral gap.

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?

Three labelled lines, front-loaded with purpose, then the when-condition, then cost. The closing cost line is marginal but short and does not bury the safety-critical 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 destructive, single-parameter tool with an output schema and full annotation coverage, the description covers purpose, gating condition, and irreversibility. Only edge-case behavior (invalid or already-deleted IDs) is left unaddressed.

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% and the monitorIds parameter already documents the 1-10 range and its source (monitor_list). The description adds no additional parameter meaning, so the baseline of 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?

The description gives a specific verb and resource ("Delete saved monitors") plus the important scope detail that it removes "everything they collected." That scope distinguishes it from monitor_update or monitor_get without naming them, so it stops just short of explicit sibling differentiation.

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?

"When: Only when the user asks to delete them" is a real gating condition that tells the agent not to infer deletion intent. It does not name alternatives such as pausing via monitor_update, so there is clear context but no exclusion routing.

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