Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

config_profiles_delete

Delete a config profile by UUID to remove it from the Remnawave VPN panel. Provide the profile UUID to permanently remove the configuration.

Instructions

Delete a config profile

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": {
      "uuid": "<uuid>"
    },
    "name": "config_profiles_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesProfile UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are present, so the description must disclose behavioral traits. It merely states 'Delete', implying destructive action, but fails to mention irreversibility, side effects (e.g., impact on nodes or users using the profile), permission requirements, or cascading behavior. This is a significant gap for a destructive operation.

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

Conciseness4/5

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

The description is a single, clear sentence with no waste. It is appropriately sized for a simple operation. However, it lacks any additional structure or emphasis on key points, though that's not a major issue given the brevity.

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?

For a destructive tool with a single parameter and no output schema, the description is incomplete. It omits behavioral context such as irreversibility, prerequisites, or consequences. An agent cannot fully gauge the risk or proper usage from the description alone.

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 covers 100% of parameters with a description ('Profile UUID'), so the baseline is 3. The description adds nothing beyond the schema—it doesn't clarify the format, constraints, or how to obtain the UUID. With full schema coverage, a 3 is appropriate.

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 verb and resource: 'Delete a config profile'. It distinguishes itself from siblings like config_profiles_list, config_profiles_get, config_profiles_create, etc., by naming the delete action, though it doesn't explicitly contrast itself. The purpose is unmistakable.

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 provided on when to use this tool versus alternatives, nor any prerequisites or conditions. An agent receives no context about when deletion is appropriate or what to check before calling it.

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