Skip to main content
Glama

update-proxy-host

update-proxy-host

Modify an existing Nginx Proxy Manager proxy host by updating only the fields provided, including domains, forwarding, SSL, and access settings.

Instructions

Update an existing proxy host. Only provided fields are updated. Omit read-only fields (id, created_on, etc.).

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": "update-proxy-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
enabledNo
locationsNo
sslForcedNo
domainNamesNo
forwardHostNo
forwardPortNo
hstsEnabledNo
accessListIdNo
http2SupportNo
instanceNameYes
blockExploitsNo
certificateIdNo
forwardSchemeNo
advancedConfigNo
cachingEnabledNo
hstsSubdomainsNo
trustForwardedProtoNo
allowWebsocketUpgradeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, but it does add genuine behavioral information: this is a partial-update (patch-style) operation where unspecified fields are preserved. That is valuable beyond the schema, yet it omits permission/auth requirements, error behavior, and consequences for fields like certificateId or locations.

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 with the core action front-loaded and no filler. The trailing 'etc.' is the one piece of imprecision in an otherwise tight statement.

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 a 19-parameter mutation tool with no annotations and no output schema, a three-sentence description is thin — the bulk of the parameters are left entirely undocumented. An agent can identify the operation but not confidently construct a correct payload.

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 0% across 19 parameters, so the description needed to compensate and does not: it never explains 'locations' format, 'forwardPort' units, 'domainNames' ordering, or 'advancedConfig' content. The only parameter-adjacent guidance names 'id, created_on, etc.' as read-only, and 'created_on' is not even in the schema, which the vague 'etc.' leaves unresolved.

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 ('Update an existing proxy host'), which clearly distinguishes it from create/delete siblings by name alone. It does not explicitly name the alternatives (enable-proxy-host, disable-proxy-host), but the mutating intent is unambiguous.

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 explicit when-to-use guidance and no routing to alternatives; an agent cannot tell from the text whether toggling 'enabled' here versus calling enable-proxy-host/disable-proxy-host is intended. The partial-update note ('Only provided fields are updated') hints at usage but never states a condition or exclusion.

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