Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

settings_update

Change Remnawave panel settings by providing key-value pairs; the tool applies the updates directly.

Instructions

Update Remnawave panel settings

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": {
      "settings": "<settings>"
    },
    "name": "settings_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYesSettings key-value pairs to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only says 'Update' without explaining side effects, whether settings are merged or replaced, permission requirements, or reversibility. The agent is left guessing about the update semantics.

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

Conciseness3/5

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

The description is appropriately short, but it is under-specified rather than concise. It lacks structure or any attempt to convey essential information beyond a single sentence, so while it is not verbose, it fails to earn its brevity with substance.

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 settings update tool with one complex parameter and no output schema or annotations, the description is incomplete. It does not clarify what settings are available, how updates are applied, or how it differs from related settings tools, leaving critical information missing.

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 describes the 'settings' parameter as 'Settings key-value pairs to update' with additionalProperties, so coverage is 100%. The description adds no extra meaning beyond that, so it meets the baseline but does not enhance understanding of valid keys or formats.

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

Purpose3/5

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

The description states a specific verb and resource ('Update Remnawave panel settings'), which is clear at a basic level. However, it does not differentiate from sibling tools like settings_get (read) or subscription_settings_update (a distinct settings domain), leaving ambiguity about which settings are affected.

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 such as settings_get or subscription_settings_update. There are no exclusions, prerequisites, or context clues to help an agent select this tool correctly.

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