Skip to main content
Glama

list-proxy-hosts

list-proxy-hosts

Retrieve all proxy hosts from a specified Nginx Proxy Manager instance, including domains, forwarding configuration, SSL, and HSTS details for auditing or management.

Instructions

List all proxy hosts on an NPM instance. Returns full host details including domains, forwarding config, SSL, and HSTS settings.

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-proxy-hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the shape of the returned data (domains, forwarding config, SSL, HSTS), which signals a read-only enumeration, but says nothing about ordering, pagination, volume of results, or what an unknown instanceName yields.

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 operation and followed by return contents. No filler; only the return-value sentence is arguably beyond the minimum.

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 read-only list tool with one parameter and no output schema, the return-content summary is valuable, but the definition stops short of covering instanceName semantics and result-set behavior (pagination/limits), leaving real gaps for an agent calling it.

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?

The single instanceName parameter has 0% schema description coverage, and the phrase 'on an NPM instance' only hints that it selects the target instance. It does not clarify whether the value is a display name, an ID, or a URL alias, so the gap is only partially closed.

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 states a specific verb and resource ('List all proxy hosts') and scopes it to 'an NPM instance.' The word 'all' implicitly contrasts with the singular get-proxy-host sibling, but no alternative is named explicitly.

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 statement of when to use this tool versus get-proxy-host or the other list-* siblings, and no prerequisites or exclusions are given. Usage must be inferred from the tool name alone.

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