Skip to main content
Glama

disable-redirection-host

disable-redirection-host

Disable an Nginx redirection host vhost so its matched domains return a 502 error.

Instructions

Disable a redirection host vhost in Nginx (returns 502 for matched domains).

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": "disable-redirection-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that matched domains return 502 after disabling, but it does not explain permissions, reversibility, side effects on related configuration, or the response behavior.

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 definition is a single front-loaded sentence with no wasted wording; the purpose and the key 502 effect are both stated immediately.

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 required parameters that lack schema descriptions, the definition is under-complete. It gives the core purpose and one effect, but omits the information needed to understand required inputs and mutation consequences.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description does not mention either required parameter ('instanceName' and 'id') or explain what they identify or how they are formatted.

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 states a specific verb ('Disable') and a specific resource ('a redirection host vhost in Nginx'), making the operation distinguishable from enable-redirection-host by verb alone.

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?

It implies the tool is used when a redirection host should be disabled, but it gives no explicit when/when-not guidance, prerequisites, or named alternative such as delete-redirection-host or enable-redirection-host.

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