Skip to main content
Glama

get-proxy-host

get-proxy-host

Fetches a single proxy host by numeric ID for an Nginx Proxy Manager instance; use list-proxy-hosts to find the ID.

Instructions

Get a single proxy host by ID. Use list-proxy-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-proxy-host"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProxy host numeric ID
instanceNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 entire behavioral burden, and it says almost nothing beyond 'get'. It does not confirm the operation is non-mutating, nor describe behavior for a nonexistent ID, permission/auth requirements, or any side effects or rate limits.

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 purpose and followed by the one actionable hint; no filler. Slightly leaner than ideal given the undocumented instanceName parameter, but nothing is wasted.

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-record lookup with two required parameters, a 50%-covered schema, no annotations and no output schema, the definition is minimally viable but leaves an agent guessing about instanceName's meaning and how failures surface. Enough to call it, not enough to call it confidently in all cases.

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?

Schema coverage is only 50%: 'id' is documented in the schema and echoed by the description, while 'instanceName' is unexplained in both places. The pointer to 'list-proxy-hosts' adds real value for sourcing the ID value, but nothing is said about what instanceName selects (server/instance scoping).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 proxy host by ID') and explicitly separates itself from the list variant by name, so an agent can distinguish it from 'list-proxy-hosts' and the redirection-host siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete workflow rule: use 'list-proxy-hosts' to obtain the ID first, which is the main practical precondition for calling this tool. It stops short of stating when this tool is inappropriate (e.g. missing/unknown IDs, error behavior), so it is clear context rather than full when/when-not guidance.

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