Skip to main content
Glama

create-proxy-host

create-proxy-host

Create a new Nginx Proxy Manager proxy host by specifying domain names, backend scheme, host, and port, with optional SSL, HSTS, caching, and websocket settings.

Instructions

Create a new proxy host. Domain names, forward host/port, and scheme are required. SSL, HSTS, caching, and websocket options available.

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>",
      "domainNames": "<domainNames>",
      "forwardScheme": "<forwardScheme>",
      "forwardHost": "<forwardHost>",
      "forwardPort": "<forwardPort>"
    },
    "name": "create-proxy-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
locationsNoJSON array of location objects
sslForcedNo
domainNamesYesList of domain names (e.g. ["app.example.com"])
forwardHostYesBackend hostname or IP
forwardPortYesBackend port
hstsEnabledNo
accessListIdNo
http2SupportNo
instanceNameYes
blockExploitsNo
certificateIdNo
forwardSchemeYes
advancedConfigNo
cachingEnabledNo
hstsSubdomainsNo
trustForwardedProtoNo
allowWebsocketUpgradeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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, and it falls well short: it never says this is a write/mutating operation, whether it is idempotent, what happens when certificateId or accessListId is left at 0, or what a successful response contains. 'SSL options available' gestures at behavior without explaining the coupling between sslForced, certificateId, and hstsEnabled.

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?

Three short sentences, front-loaded with the action and required inputs before the optional surface. Efficient, though the final sentence is a bare feature list that adds little precision.

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?

For an 18-parameter mutating tool with no annotations and no output schema, the description is far too thin — it omits prerequisite/setup behavior, certificate coupling, defaults for the 13 optional parameters, and any notion of the returned resource. An agent could invoke it but would likely misconfigure or need to guess.

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 only 22% across 18 parameters, so the description should compensate but does not. It names four option families (SSL, HSTS, caching, websocket) but gives no meaning for the many undocumented parameters such as enabled, accessListId, certificateId, locations, advancedConfig, http2Support, blockExploits, or trustForwardedProto.

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 ('Create a new proxy host') and lists the required inputs (domain names, forward host/port, scheme), so the agent knows exactly what gets created. It does not distinguish itself from sibling create-redirection-host or explain when a proxy host is preferred over a 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 when-to-use guidance, no prerequisites (e.g. whether a certificate must exist first, or that instanceName refers to the NPM instance), and no mention of alternatives such as create-redirection-host. The only usage signal is an implicit one derived from the required-field list.

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