Skip to main content
Glama
devhelmhq

DevHelm MCP Server

Official
by devhelmhq

delete_monitor

Permanently delete a monitor by providing its unique ID, stopping all tracking and alerting for that resource.

Instructions

Delete a monitor permanently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monitor_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual implementation of the delete_monitor tool. It uses @mcp.tool() decorator to register as an MCP tool, takes a monitor_id and optional api_token, calls get_client(api_token).monitors.delete(monitor_id), and returns a plain string 'Monitor deleted successfully.' on success or raises a tool error on DevhelmError.
    @mcp.tool()
    def delete_monitor(monitor_id: str, api_token: str | None = None) -> str:
        """Delete a monitor permanently."""
        try:
            get_client(api_token).monitors.delete(monitor_id)
            return "Monitor deleted successfully."
        except DevhelmError as e:
            raise_tool_error(e)
  • The tool is registered via the @mcp.tool() decorator on the delete_monitor function. This happens inside the register(mcp) function which is called from server.py.
    @mcp.tool()
  • The monitors module's register() function is called with the mcp FastMCP instance, which registers all monitor tools including delete_monitor.
    for mod in ALL_TOOL_MODULES:
        mod.register(mcp)
  • Imports used by delete_monitor: DevhelmError from devhelm, and get_client, raise_tool_error from devhelm_mcp.client.
    """Monitor tools — HTTP, DNS, TCP, ICMP, MCP, and Heartbeat monitors."""
    
    from __future__ import annotations
    
    from typing import Any
    
    from devhelm import DevhelmError
    from devhelm.types import CreateMonitorRequest, UpdateMonitorRequest
    from fastmcp import FastMCP
    from pydantic import Field
    
    from devhelm_mcp.client import (
        ToolResult,
        as_payload,
        get_client,
        raise_tool_error,
        serialize,
    )
Behavior3/5

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

No annotations provided. Description mentions 'permanently', indicating irreversibility, but does not detail side effects (e.g., whether dependent resources are removed, immediate vs. scheduled deletion). Minimal behavioral context.

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?

Extremely concise: four words that capture the core action. No unnecessary content; every word earns its place.

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?

Output schema exists but its content is unknown; description does not explain return values or error conditions. For a permanent deletion tool with many siblings, more context (e.g., cascading effects, confirmation steps) would improve completeness.

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

Parameters1/5

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

Input schema has 0% description coverage. The description adds no meaning beyond the schema (only provides parameter name 'monitor_id'). Fails to clarify format, expected values, or how to obtain the ID.

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?

Description clearly states 'Delete a monitor permanently', which is a specific verb and resource. It distinguishes from sibling tools like 'pause_monitor' (temporary suspension) and 'create_monitor' (creation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., disabling or pausing). Lacks context about prerequisites or consequences (e.g., data loss, impact on alerts).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devhelmhq/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server