Skip to main content
Glama
Sign In
Nginx Proxy Manager MCP

Nginx Proxy Manager MCP

by VeryBigSad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_redirection_host

Retrieve a specific redirection host by its ID to view or manage its configuration in Nginx Proxy Manager.

Instructions

Get a specific redirection host by ID

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": {
      "host_id": "<host_id>"
    },
    "name": "get_redirection_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe ID of the redirection host

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.14.0

TDQS

A3.6/5.0
Behavior3/5

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

Since no annotations are provided, the description carries the burden of behavioral transparency. It is minimal and does not disclose error handling (e.g., behavior when host_id not found), return format, or authentication requirements. For a simple get operation, this is acceptable but not fully transparent.

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 with no unnecessary words. It is front-loaded with the action and resource, making it highly concise and efficient.

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

Completeness4/5

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

For a simple retrieval tool with one parameter and no output schema, the description is mostly complete. It could be improved by mentioning the return type or behavior on missing ID, but it adequately covers the primary function.

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

Parameters3/5

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

With 100% schema description coverage, the baseline is 3. The tool description adds no further meaning to the parameter beyond what the input schema already provides, so no extra value.

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 'Get a specific redirection host by ID' clearly states the action (get), the resource (redirection host), and the identifier (ID). It distinguishes well from sibling tools like list_redirection_hosts or create_redirection_host.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, such as list_redirection_hosts for multiple results, nor does it mention any preconditions or limitations.

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