Skip to main content
Glama
TrackLine
by TrackLine

nodes_restart

Restart a specific node in the Remnawave VPN panel to resolve connectivity issues or apply configuration changes.

Instructions

Restart a specific node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesNode UUID

Implementation Reference

  • The implementation of the 'nodes_restart' tool, which uses the RemnawaveClient to restart a node by UUID.
    server.tool(
        'nodes_restart',
        'Restart a specific node',
        {
            uuid: z.string().describe('Node UUID'),
        },
        async ({ uuid }) => {
            try {
                const result = await client.restartNode(uuid);
                return toolResult(result);
            } catch (e) {
                return toolError(e);
            }
        },
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this requires admin permissions, if it causes service interruption, what the restart process entails, expected downtime, or error conditions. For a potentially disruptive operation, this is inadequate.

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's appropriately sized for a simple operation and front-loads the essential information (restart + specific node).

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 potentially disruptive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral implications, permissions needed, expected outcomes, or error handling. Given the complexity of node management and sibling tools offering related functions, more context is needed.

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 'uuid' parameter fully documented as 'Node UUID'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or where to find the UUID. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Restart a specific node' clearly states the action (restart) and target resource (node), with 'specific' implying individual node targeting. It distinguishes from sibling 'nodes_restart_all' by specifying individual vs. bulk operation, though it doesn't explicitly name the sibling alternative.

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 about when to use this tool versus alternatives like 'nodes_restart_all' for bulk operations, 'nodes_disable'/'nodes_enable' for state changes, or 'nodes_reset_traffic' for traffic management. The description implies individual node targeting but offers no explicit usage context or prerequisites.

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