Skip to main content
Glama
Maaagiic

mcp-remnawave

by Maaagiic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

users_create

Creates a new VPN user account in Remnawave panel, auto-generating credentials unless you supply them explicitly.

Instructions

Create a user. Credentials (vlessUuid/ssPassword/trojanPassword/shortUuid) are generated by the panel unless given — pass them explicitly for service users.

Input Schema

NameRequiredDescriptionDefault
tagNoOptional. User tag for categorization. Max 16 characters, uppercase letters, numbers and underscores only.
emailNoOptional. User email address. Must be a valid email format.
statusNoOptional. User account status. Defaults to ACTIVE.ACTIVE
expireAtYesAccount expiration date. Required. Format: 2025-01-17T15:38:45.065Z
usernameYesUnique username for the user. Required. Must be 3-36 characters long and contain only letters, numbers, underscores and dashes.
createdAtNoOptional. Account creation date. Format: 2025-01-17T15:38:45.065Z
shortUuidNoOptional. Short UUID identifier for the user.
vlessUuidNoOptional. UUID for VLESS protocol. Must be a valid UUID format.
ssPasswordNoOptional. Password for Shadowsocks protocol. Must be 8-32 characters.
telegramIdNoOptional. Telegram user ID for notifications. Must be an integer.
descriptionNoOptional. Additional notes or description for the user account.
trojanPasswordNoOptional. Password for Trojan protocol. Must be 8-32 characters.
hwidDeviceLimitNoOptional. Maximum number of hardware devices allowed. Must be a positive integer.
externalSquadUuidNoOptional. External squad UUID.
trafficLimitBytesNoOptional. Traffic limit in bytes. Set to 0 for unlimited traffic.
lastTrafficResetAtNoOptional. Date of last traffic reset. Format: 2025-01-17T15:38:45.065Z
activeInternalSquadsNoOptional. Array of UUIDs representing enabled internal squads.
trafficLimitStrategyNoAvailable reset periodsNO_RESET

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-read, non-destructive write, so the bar is lower; the description still adds a genuinely non-obvious behavior — that vlessUuid/ssPassword/trojanPassword/shortUuid are auto-generated by the panel unless supplied. It stops short of covering side effects (subscription creation, permission requirements), keeping it out of 5 territory.

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?

Two tight sentences, zero filler. The core action is front-loaded and the non-obvious credential behavior follows immediately.

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 an 18-parameter mutation tool with no output schema and thin annotations, the description covers the single most important operational fact (credential defaults) but omits permissions, side effects, and result behavior. Adequate minimum-viable coverage, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, but the description adds meaning the schema does not: it groups the four credential parameters and explains they are safe to omit because they are auto-generated. That materially improves parameter decisions for those four fields.

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?

States a clear verb+resource ('Create a user') that an agent can readily distinguish from users_update and the many bulk/read siblings. It does not explicitly name an alternative tool, so it stays below the sibling-differentiating bar of a 5.

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 only conditional offered is when to supply credentials explicitly ('for service users'). There is no guidance on when to use this versus users_bulk_update, squads_add_many_users, or other creation paths, and no prerequisites or exclusions are stated.

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