Skip to main content
Glama
Sign In
Nginx Proxy Manager MCP

Nginx Proxy Manager MCP

by VeryBigSad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_dead_host

Remove a dead host from Nginx Proxy Manager by providing its ID to clean up unused proxy configurations.

Instructions

Delete a dead host by ID

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": {
      "host_id": "<host_id>"
    },
    "name": "delete_dead_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe ID of the dead host to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.14.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must convey behavioral traits but only states 'Delete'. It lacks detail on whether deletion is irreversible, required permissions, or side effects. The minimal info forces the agent to assume standard delete behavior without confirmation.

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?

The description is a single sentence, highly concise and front-loaded. Every word is essential, and it immediately conveys the core function.

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 simple deletion tool with one parameter and no output schema, the description is almost sufficient. It covers purpose and key input. A small improvement could mention irreversibility, but overall it's complete enough given the low complexity.

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?

The input schema covers the parameter fully with a description 'The ID of the dead host to delete'. The tool description adds no extra meaning, but schema coverage is 100%, meeting the baseline. No further semantic enrichment is provided.

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?

The description 'Delete a dead host by ID' clearly states the verb (delete) and resource (dead host), distinguishing it from sibling tools like delete_proxy_host. The specificity of 'dead host' makes the purpose unambiguous.

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 usage context is provided. The description does not specify when to use this tool versus alternatives such as disable_dead_host, nor does it mention prerequisites or consequences. The sibling list implies different entity types, but no explicit guidance is given.

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

Deploy Server

Other Tools