Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

users_delete

Permanently remove a user from Remnawave by specifying their numeric user ID. Use this to delete an unwanted or inactive user account.

Instructions

Permanently delete a Remnawave user

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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser numeric ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The word 'permanently' adds an important behavioral trait beyond the tool name: the deletion is irreversible. However, with no annotations provided, the description carries the full burden and does not mention other behavioral consequences such as cascading effects on subscriptions, tokens, or associated records.

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, front-loaded sentence with no filler. 'Permanently' earns its place by conveying irreversibility, and every word contributes to understanding the operation.

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 tool with one fully documented parameter and no nested objects or output schema, the description plus schema is largely sufficient for an agent to invoke it correctly. The main missing context is when to use this versus the other delete/disable variants, but the operation itself is simple and clear.

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 single required parameter userId is already described as 'User numeric ID to delete'. The tool description adds no additional parameter meaning, so the baseline score of 3 applies.

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 uses a specific verb ('delete') and resource ('Remnawave user'), and 'permanently' clarifies the exact scope of the operation. It clearly distinguishes this single-user delete from sibling operations like users_bulk_delete.

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 gives no guidance on when to use this tool versus alternatives such as users_bulk_delete, users_bulk_delete_by_status, or users_disable. There is no explicit condition, prerequisite, or exclusion to help an agent choose correctly among the many user-related siblings.

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