Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Delete Proxy

deleteProxy
Destructive

Permanently deletes a proxy by its ID while keeping associated monitors, which then send requests directly. Use listProxies to find the proxyID.

Instructions

Permanently deletes a proxy. Monitors that used it are kept and send their requests directly from then on. Find the ID with listProxies.

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": {
      "proxyID": "<proxyID>"
    },
    "name": "deleteProxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
proxyIDYesThe ID of the proxy to delete

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real value by disclosing the cascade semantics: referencing monitors survive and begin sending requests directly, which is exactly the post-deletion behavior an agent cannot infer from structured fields.

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?

Three short sentences, front-loaded with the destructive action, then consequence, then ID discovery. Every sentence carries distinct information with no redundancy.

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 single-parameter destructive tool with an output schema, the definition covers action, irreversibility, side effects on dependents, and ID sourcing. Only a mention of error conditions for an unknown or in-use proxyID is missing.

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?

Schema coverage is 100% with a clear proxyID description, so the baseline is satisfied by the schema alone. The description still adds procedural meaning by telling the agent where to obtain a valid ID (listProxies) before calling.

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 deletes a proxy') and immediately names the sibling to consult for the identifier. An agent can tell this apart from deleteMonitor, deleteNotification and the other delete siblings without opening the schema.

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?

Gives a clear use condition (deleting a proxy) and an actionable prerequisite step ('Find the ID with listProxies'), which routes the agent to the correct sibling for discovery. It stops short of any when-not guidance such as preferring updateProxy when only configuration needs changing.

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