mcp-remnawave

metadata_node_upsert

Create or update metadata key-value pairs for a specific node in a Remnawave VPN panel, enabling dynamic configuration and management.

Instructions

Create or update metadata for a node

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>",
      "metadata": "<metadata>"
    },
    "name": "metadata_node_upsert"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes	Node UUID
`metadata`	Yes	Metadata key-value pairs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Create or update' and does not clarify whether metadata is merged or fully replaced, what happens to existing metadata, or how errors like an unknown UUID are handled.

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?

A single sentence with zero wasted words; the verb and target are front-loaded. It is appropriately sized for a straightforward upsert operation.

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?

There is no output schema and no annotations, so the description is the only context an agent gets. It omits merge/replace semantics, error behavior, and any note that this is a mutating operation on node metadata, leaving meaningful gaps for a tool this simple.

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%, with both uuid ('Node UUID') and metadata ('Metadata key-value pairs') already documented in the schema. The description adds no parameter meaning beyond the schema, so the baseline 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?

States the precise verb ('Create or update') and resource ('metadata for a node'), which clearly differentiates it from siblings like metadata_user_upsert and metadata_node_get. The scope is unambiguous and immediately understandable.

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 given on when to use this tool versus alternatives such as metadata_user_upsert or metadata_node_get. It does not state any conditions, prerequisites, or exclusions (e.g., that the node must already exist).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server