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

@kognar/nginx-manager-mcp-server

by kognar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Enable proxy host

npm_enable_proxy_host

Enable a proxy host by its ID to resume traffic routing through Nginx Proxy Manager.

Instructions

Enable 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": {
      "id": "<id>"
    },
    "name": "npm_enable_proxy_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It fails to mention that the proxy host must exist, that enabling is reversible, or any required permissions. The minimal description does not compensate for the lack of annotations.

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

Conciseness3/5

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

The description is extremely concise at one sentence, but it is under-specified. While there is no waste, the lack of detail makes it less useful. A balance between conciseness and informativeness is missing.

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?

Given the absence of annotations and output schema, the description is far from complete. It does not address what happens after enabling, error conditions, or the state change. Competes with many sibling tools but offers no unique context.

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 the description should explain the parameter 'id'. It does not mention that id refers to the proxy host ID. The schema itself is sparse, and the description adds no value beyond what the name implies.

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 'Enable a proxy host.' clearly states the action (enable) and resource (proxy host), distinguishing it from siblings like create, delete, disable, and list. However, it lacks additional context about what enabling entails.

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 like npm_create_proxy_host (to create) or npm_disable_proxy_host. There is no mention of prerequisites or when not to use.

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