Skip to main content
Glama

enable-redirection-host

enable-redirection-host

Enables a disabled Nginx redirection host vhost in Nginx Proxy Manager, allowing its redirect rules to take effect again.

Instructions

Enable a disabled redirection 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-redirection-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 burden. It implies a mutation but does not disclose what happens if the host is already enabled, whether an Nginx reload/restart occurs, required permissions, 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 tight sentence with the verb and scope front-loaded and no filler. It is concise rather than bloated; the shortfall is under-specification, not verbosity.

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 mutation tool with no annotations, no output schema, and two completely undescribed parameters, the description should cover state preconditions, side effects, and failure modes. It provides none of these, leaving the agent with only the tool name to work from.

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 (id and instanceName) are undocumented in the structured fields, and the description adds no meaning for either. It doesn't say whether 'id' is a numeric ID or slug, or what instanceName identifies.

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: enabling a disabled redirection host vhost in Nginx. The word 'disabled' implicitly distinguishes it from disable-redirection-host and update-redirection-host, though it never names or contrasts those siblings explicitly.

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?

Usage is only implied: 'Enable a disabled redirection host' suggests calling this when a host is in a disabled state, but it gives no explicit when-to-use/when-not-to-use guidance, no prerequisites, and no pointer to disable-redirection-host as the inverse operation.

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