List all 404 dead hosts configured in Nginx Proxy Manager to find broken proxy entries and clean them up. Filter by keyword or expand related objects.
List all 404 dead hosts configured in Nginx Proxy Manager
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Search/filter keyword | |
| expand | No | Comma-separated related objects to expand |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It implies a read-only, unpaginated enumeration via 'List all', but says nothing about whether disabled hosts are included, ordering, pagination limits, or whether auth/scope is required.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero filler; the resource and scope are stated immediately with no redundant restatement of the name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, no-required-parameter list tool with full schema coverage and no output schema, the description is minimally sufficient. However, with no annotations at all it leaves the read-only/safety profile and the shape of the returned host list entirely unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and both parameters (query, expand) are documented in the schema, so the baseline of 3 applies. The description adds no syntax or format detail about filtering or expansion beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) plus resource (404 dead hosts in Nginx Proxy Manager), which cleanly separates it from the get/create/update/delete/enable/disable dead-host siblings and from other npm_list_* tools. An agent can select it without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no mention of prerequisites or alternatives (e.g. npm_get_dead_host for a single host). The only implied usage is 'I want the whole collection', which the agent must infer from the verb 'List'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.