Retrieve a node plugin shared list by its name to get its configuration details. Use this to fetch exactly the list you need for managing VPN node plugins.
Get a node plugin shared list by name
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Shared list name |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. 'Get' signals a non-mutating read and 'by name' scopes the lookup, but there is no disclosure of not-found behavior, uniqueness guarantees, or error cases. For a trivial getter this is adequate, though not richly transparent.
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?
One short, front-loaded sentence with no filler; the verb and object appear first and every word contributes. It is appropriately sized for a single-parameter getter.
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 1-parameter getter with no output schema, the description plus schema is largely sufficient to make the call correctly. It could be more complete by clarifying name uniqueness across node plugins and explicitly routing to shared_lists_list when enumerating, but these are minor given the low complexity.
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?
The only parameter, name, is fully described in the schema as 'Shared list name', and the description adds no additional meaning beyond 'by name'. Since schema coverage is 100%, the baseline 3 applies; no extra format, case-sensitivity, or scoping details are provided.
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?
Description states a specific verb ('Get'), a specific resource ('node plugin shared list'), and the lookup key ('by name'), which distinguishes it from the sibling shared_lists_list enumeration tool. It is immediately actionable for an agent deciding between get-by-name and list-all operations.
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 explicit when-to-use or named alternative is given, but the phrase 'by name' implicitly signals this tool is for retrieving a single known shared list rather than enumerating them. It does not explicitly direct the agent to shared_lists_list when the name is unknown, so the guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.