Skip to main content
Glama

get-redirection-host

get-redirection-host

Retrieve a single Nginx Proxy Manager redirection host by its numeric ID and instance name. Use list-redirection-hosts first to find the ID.

Instructions

Get a single redirection host by ID. Use list-redirection-hosts to find the 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": {
      "instanceName": "<instanceName>",
      "id": "<id>"
    },
    "name": "get-redirection-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRedirection host numeric ID
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. Beyond the implied read-only nature of "Get", it says nothing about permissions, not-found/error behavior, or return shape for a lookup tool.

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?

Two short sentences, front-loaded with the core action and followed by the practical tip. No filler, though it is terse enough to leave gaps rather than padding.

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 two-parameter lookup with no output schema this is close to sufficient, but the undocumented `instanceName` parameter and the absence of any error/return context leave real holes.

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 coverage is only 50%: `id` is documented but `instanceName` has no description in the schema and is never explained in the description. The description adds only the hint on how to obtain the ID, leaving one required parameter undefined.

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 ("Get a single redirection host by ID"), which clearly separates it from list/create/update/delete siblings. It does not explicitly contrast with get-proxy-host or get-certificate, but the resource noun does that work.

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?

Gives a concrete pointer to `list-redirection-hosts` for discovering the ID, which is genuine usage guidance. It does not say when to prefer this over other retrieval paths or what happens if the ID is unknown/invalid.

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