Skip to main content
Glama

delete-proxy-host

delete-proxy-host

Deletes a proxy host by ID from a specified Nginx Proxy Manager instance and removes its Nginx vhost configuration.

Instructions

Delete a proxy host by ID. Removes the Nginx vhost configuration.

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": {
      "instanceName": "<instanceName>",
      "id": "<id>"
    },
    "name": "delete-proxy-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses only that the Nginx vhost config is removed. It does not say whether the operation is irreversible, what happens to associated certificates or traffic, whether elevated permissions are required, or what the response looks like.

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?

Two short sentences with the destructive action front-loaded and no filler. "by ID" is mildly redundant with the schema, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, unannotated two-parameter tool with zero schema documentation, the description is thin: it omits irreversibility, prerequisites, the instanceName parameter, and any indication of the return value. An agent has enough to identify the tool but not enough to call it safely.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only implies that `id` identifies the host. The required `instanceName` parameter is never mentioned, leaving the agent to guess that it selects which Nginx Proxy Manager instance to act against.

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?

States a specific verb and resource ("Delete a proxy host by ID") and adds the concrete side effect ("Removes the Nginx vhost configuration"). The resource is clearly distinct from the redirection-host and certificate siblings, though the description never explicitly contrasts itself with them.

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 versus disable-proxy-host (a reversible alternative) or update-proxy-host. There are no stated preconditions, no warnings about confirming intent, and no mention of what to do about certificates attached to the host.

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