Skip to main content
Glama

enable-proxy-host

enable-proxy-host

Activates a disabled Nginx Proxy Manager proxy host on a specified instance so it can resume routing traffic.

Instructions

Enable a disabled proxy host vhost in Nginx.

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": "enable-proxy-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely drops it. It does not state whether the operation is idempotent, what happens if the host is already enabled, whether an Nginx reload occurs, what permissions or auth are needed, or whether the change is reversible.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is partly under-specification rather than disciplined editing.

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 state-mutating tool with no annotations, no output schema, and two undocumented required parameters, the description is too thin. An agent cannot tell what a success response looks like, how failures are surfaced, or what 'instanceName' scopes the operation to.

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 both required parameters are undocumented in structured data, and the description supplies essentially no meaning for them. Only 'id' is weakly inferable as the proxy host being enabled; 'instanceName' is completely unexplained (Nginx instance? manager instance?) and is required.

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?

The description names a specific verb and resource ('Enable a disabled proxy host vhost in Nginx'), which is far more informative than the tautological name/title. It implicitly distinguishes itself from its inverse, disable-proxy-host, but never names any sibling explicitly, so an agent must infer the pairing.

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

Usage Guidelines3/5

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

The phrase 'a disabled proxy host' implies the precondition that the host is currently disabled, which is a usable cue. However, there is no guidance on what to do instead if the host is already enabled, no mention of disable-proxy-host as the reverse operation, and no error/precondition handling described.

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