Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

users_enable

Enable a disabled Remnawave user to restore VPN access. Provide the user's numeric ID to reactivate the account.

Instructions

Enable a disabled Remnawave user (restore VPN access)

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": {
      "userId": "<userId>"
    },
    "name": "users_enable"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser numeric ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description must carry the burden of behavioral transparency. It states the action (enable) and the effect (restore VPN access), which is a positive behavioral disclosure, but it does not mention any side effects, permissions required, or reversibility. The description is consistent with the action of enabling a user.

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, concise sentence that front-loads the key action and outcome. It contains no redundancy, making it highly efficient and well-structured.

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

Completeness4/5

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

For a simple tool with a single parameter and no output schema, the description is complete for basic invocation. It lacks detail on what happens if the user is already enabled or if the user does not exist, but these are edge cases. The presence of a clear outcome statement (restore VPN access) covers the essential need.

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 description coverage is 100%, so the 'userId' parameter is fully documented in the schema: 'User numeric ID'. The description does not add additional semantic value beyond the schema, but the schema is already clear. This is a baseline score as schema carries the load.

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

Purpose5/5

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

The description clearly states the verb 'Enable' and the resource 'disabled Remnawave user', and specifies the outcome 'restore VPN access'. This distinguishes it from the sibling tools like users_disable, users_create, users_update, and others.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for enabling previously disabled users, but does not explicitly state when to use it over other user management tools (e.g., users_update) or what prerequisites might exist. It provides minimal guidance on the exact context of use.

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