Skip to main content
Glama
TrackLine

remnawave-mcp

by TrackLine
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

nodes_enable

Activate a disabled VPN node by providing its UUID to restore connectivity and functionality within the network.

Instructions

Enable a disabled node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesNode UUID

Implementation Reference

  • src/tools/nodes.ts:176-183 (handler)
    The handler function for the 'nodes_enable' tool, which calls the client's enableNode method.
    async ({ uuid }) => {
    try {
        const result = await client.enableNode(uuid);
        return toolResult(result);
    } catch (e) {
        return toolError(e);
    }
},
  • src/tools/nodes.ts:170-184 (registration)
    Tool registration for 'nodes_enable' using the server.tool method.
    server.tool(
    'nodes_enable',
    'Enable a disabled node',
    {
        uuid: z.string().describe('Node UUID'),
    },
    async ({ uuid }) => {
        try {
            const result = await client.enableNode(uuid);
            return toolResult(result);
        } catch (e) {
            return toolError(e);
        }
    },
);
  • src/tools/nodes.ts:173-175 (schema)
    Input schema definition for 'nodes_enable', requiring a 'uuid' string.
    {
    uuid: z.string().describe('Node UUID'),
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks behavioral details: no mention of permissions required, whether the change is immediate or requires restart, what happens on success/failure, or if it affects connected users. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It is front-loaded with the core action and target, making it immediately understandable without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., side effects, error conditions), usage context, and expected outcomes. Given the complexity of enabling a system node, more guidance is needed for safe and effective use.

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 description coverage is 100%, with the single parameter 'uuid' documented as 'Node UUID'. The description adds no additional parameter context beyond implying the UUID belongs to a disabled node. Baseline 3 is appropriate since the schema fully describes the parameter.

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?

The description 'Enable a disabled node' clearly states the action (enable) and target resource (node), with the qualifier 'disabled' indicating the precondition. It distinguishes from sibling 'nodes_disable' by specifying the opposite operation, though it doesn't explicitly differentiate from other node-related tools like 'nodes_restart' or 'nodes_update'.

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?

No guidance is provided on when to use this tool versus alternatives. While 'disabled' implies a precondition, there's no mention of prerequisites (e.g., node must exist and be disabled), exclusions (e.g., cannot enable an already enabled node), or related tools like 'nodes_disable' for the reverse operation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TrackLine/mcp-remnawave'

If you have feedback or need assistance with the MCP directory API, please join our Discord server