Retrieves details of a specific Nginx Proxy Manager stream by ID, optionally expanding related objects. Use it to inspect stream configuration for troubleshooting or management.
Get details of a specific stream by ID
| Name | Required | Description | Default |
|---|---|---|---|
| expand | No | Comma-separated related objects to expand | |
| stream_id | Yes | The ID of the stream |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full burden. The verb 'Get' does convey a non-mutating read, which is the main behavioral fact here, but nothing is said about permissions, error behavior for unknown IDs, 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; every word (verb, resource, key) earns its place.
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 two-parameter read tool with a fully described schema and no output schema, the description is minimally adequate but leaves the expand parameter's effect and any failure modes unexplained.
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 coverage is 100%, so both stream_id and expand are already documented in the schema. The description's 'by ID' only restates what the schema says and adds nothing about the expand parameter, so the baseline 3 applies.
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 (Get) and resource (stream) with the keying dimension (by ID), so the agent can distinguish it from the many mutating siblings like npm_update_stream and npm_delete_stream. It does not, however, explicitly contrast itself with npm_list_streams or any other read tool.
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?
The description gives no when-to-use guidance and names no alternatives. An agent must infer from the name alone that this is the single-record counterpart to npm_list_streams.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.