Skip to main content
Glama
Sign In
Nginx Proxy Manager MCP

Nginx Proxy Manager MCP

by VeryBigSad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

disable_proxy_host

Disable a specific proxy host by providing its ID to block traffic and remove it from active configuration.

Instructions

Disable a proxy host

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": "disable_proxy_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe ID of the proxy host to disable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.14.0

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations, the description carries the full burden but provides no behavioral details. It does not explain the effect of disabling, reversibility, required permissions, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence that repeats the tool name. While brief, it fails to add value and is not sufficiently informative.

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

Completeness1/5

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

Given the presence of many sibling tools and the lack of output schema, the description is severely incomplete. It should at least explain the concept of disabling and its implications.

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 coverage is 100% (host_id is described in the schema). The description adds no additional meaning beyond what is already in the schema, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Disable a proxy host' is a tautology of the tool name. It does not specify what disabling entails or differentiate it from other disable tools like disable_dead_host or disable_redirection_host.

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 is provided on when to use this tool versus alternatives (e.g., enable_proxy_host, delete_proxy_host). The context for usage is entirely absent.

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