Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

nodes_restart

Restart a specific VPN node using its UUID, with an option to force restart when the node is unreachable.

Instructions

Restart a specific node

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uuid": "<uuid>"
    },
    "name": "nodes_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesNode UUID
forceRestartNoForce restart even if the node is unreachable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.1/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 the full burden. It only states the action 'restart' without disclosing consequences such as dropped connections, downtime, or whether forceRestart changes behavior significantly. For a mutating operation, this is insufficient.

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 only four words and is entirely front-loaded, conveying the core operation immediately. There is no fluff or redundancy; every word contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with only two parameters, but given no annotations and no output schema, the description still feels thin. It is minimally adequate for invoking the tool correctly, but fails to explain the operational impact or why an agent might choose this over nodes_restart_all.

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?

The schema covers both parameters with descriptions (100% coverage), so the description does not need to add much. The description itself does not elaborate on parameter semantics, but the baseline of 3 applies because the schema is complete.

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' gives a clear verb and resource, and the word 'specific' implicitly distinguishes it from the sibling tool nodes_restart_all. However, it doesn't go further to explicitly differentiate from other node-related tools.

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?

The description provides no explicit guidance on when to use this tool vs alternatives. The word 'specific' only hints that it is for a single node, but there is no mention of nodes_restart_all or conditions like 'use when restarting one node rather than all.'

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

Deploy Server

Other Tools