Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

node_plugins_reorder

Reorder plugins on a Remnawave VPN node by providing an ordered array of plugin UUIDs to set their sequence.

Instructions

Reorder node plugins

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": {
      "uuids": "<uuids>"
    },
    "name": "node_plugins_reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidsYesOrdered array of plugin UUIDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states the action without explaining effects (e.g., whether the entire order is replaced, whether it's reversible, or if any validation occurs). For a mutation tool, this is severely lacking.

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

Conciseness2/5

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

The description is a single clause with no structure or additional context. While it is concise, it is under-specified and provides no front-loaded value beyond the name.

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?

Despite having only one parameter and no output schema, the description omits essential context: what 'reorder' entails (e.g., does it set the full order or append?), any side effects, and how it relates to the many sibling reorder tools. This is inadequate for correct usage.

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 fully describes the single parameter 'uuids' as an ordered array of plugin UUIDs (100% coverage). The description adds no extra semantic detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Reorder node plugins' simply restates the tool name. It provides no additional specificity beyond the verb and resource, making it a tautology. It does not differentiate from sibling reorder tools like nodes_reorder or config_profiles_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?

No guidance is given on when to use this tool or how it differs from other reorder operations. There is no mention of alternatives or context such as prerequisites or ordering constraints.

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