Skip to main content
Glama
Sign In
@kognar/nginx-manager-mcp-server

@kognar/nginx-manager-mcp-server

by kognar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Disable redirection host

npm_disable_redirection_host

Disable a specific redirection host by its ID to stop traffic redirection.

Instructions

Disable a redirection 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": {
      "id": "<id>"
    },
    "name": "npm_disable_redirection_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

The description only says 'disable' with no details on side effects, immediacy, or permissions required. Since no annotations exist, the description carries full burden but fails to disclose behavioral traits beyond the verb.

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 description is a single sentence of 4 words, extremely concise and front-loaded. Every word is necessary and earns its place.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is minimally adequate but lacks context about what 'disable' entails (e.g., impact on redirection, success/failure communication). It is incomplete for an agent without domain knowledge.

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?

The input schema has one integer parameter 'id' with no description, and the tool description does not mention it at all. With 0% schema coverage, the description should compensate by explaining the parameter's role, but it does not.

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 clearly states the verb 'disable' and the resource 'redirection host', making the action clear. However, it does not distinguish this tool from sibling tools like disable_dead_host or disable_proxy_host, which have identical phrasing.

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 or when not to. There is no mention of prerequisites, reversibility, or comparison to alternative tools like enable_redirection_host.

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