Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

metadata_user_upsert

Create or update key-value metadata for a specific user in the Remnawave VPN panel by providing the user's numeric ID and metadata object.

Instructions

Create or update metadata for a 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>",
      "metadata": "<metadata>"
    },
    "name": "metadata_user_upsert"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser numeric ID
metadataYesMetadata key-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states the mutation intent but does not explain whether the metadata object is merged or fully replaced, whether existing keys are preserved, or what happens on conflicts. This is a significant gap for an upsert 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 concise sentence with no wasted words. It is front-loaded with the action, though it lacks some behavioral detail that would make it more useful.

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 a simple two-parameter upsert, the description is minimally adequate. However, the absence of annotations, output schema, and merge/replace semantics leaves the agent uncertain about important execution behavior. More context is needed for fully confident invocation.

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 coverage is 100%, so userId and metadata are already documented with descriptions. The description adds no additional parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific verb ('Create or update') and resource ('metadata for a user'). It clearly distinguishes from siblings like metadata_user_get (read vs write) and metadata_node_upsert (user vs node).

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?

Usage context is implied: an upsert for user metadata. However, it does not explicitly state when to choose this over alternatives, nor does it mention when not to use it. No read/update/delete routing guidance is provided.

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