Skip to main content
Glama

list-redirection-hosts

list-redirection-hosts

Retrieve all redirection hosts from an Nginx Proxy Manager instance to review which domains forward to other URLs.

Instructions

List all redirection hosts on an NPM instance. Redirection hosts forward domains to another URL.

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>"
    },
    "name": "list-redirection-hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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. "List all" implies a complete, non-paginated read, but the description says nothing about permissions, whether results are filtered or paginated, or what is returned — only a definition of the resource.

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 action and followed by a useful one-line definition of the resource. No filler, though the second sentence is explanatory rather than operational.

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 single-parameter read tool with no output schema, the definition is minimally adequate. It is missing the meaning of instanceName and any hint about the returned host records, which are the two things an agent still needs.

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 single parameter instanceName has 0% schema description coverage, so the description must compensate and does not. It never explains what identifies an instance, whether it is a name, slug, or ID, or how it scopes the listing.

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?

"List all redirection hosts on an NPM instance" names a specific verb and resource, and the follow-up sentence defines what a redirection host is. The resource is distinct from the proxy-host and certificate siblings, though the description never explicitly contrasts with them.

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?

There is no guidance on when to use this versus get-redirection-host, list-proxy-hosts, or any other sibling, and no stated prerequisites such as needing a valid instance or auth. The only implied usage is "use this to enumerate all redirection hosts."

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