Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hosts_reorder

Reorder hosts in a Remnawave VPN panel by assigning each host UUID a new 0-based position to control display order.

Instructions

Reorder hosts by providing each host UUID with its new position

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": {
      "hosts": "<hosts>"
    },
    "name": "hosts_reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostsYesArray of hosts with their new positions

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 of behavioral disclosure. 'Reorder' implies mutation, but the description does not state whether the change is persistent, whether validation occurs, whether the operation is reversible, what the response looks like, or if partial orders are allowed.

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, direct sentence with no filler or redundancy. It front-loads the core action and the required input format, making it easy for an agent to parse quickly.

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?

For a simple, one-parameter tool with a detailed schema, the description is minimally adequate. However, with no annotations and no output schema, it leaves out practical context such as return values, error behavior, or whether the operation is global or scoped, so it is not fully complete.

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%, and the schema already documents 'Host UUID' and 'New position (0-based)' clearly. The description restates this idea without adding extra meaning, so it meets the baseline but does not enrich parameter understanding.

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 clearly states the action ('Reorder hosts') and the resource (hosts), with the specific mechanism of supplying UUIDs and new positions. It is unambiguous about what the tool does, though it does not explicitly contrast itself with nearby siblings like hosts_bulk_update or nodes_reorder.

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 guidance on when to use this tool versus alternatives such as hosts_bulk_update or hosts_bulk_delete. There is no mention of prerequisites, whether all hosts must be supplied, or what scenarios call for reordering vs other bulk host operations.

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