mcp-remnawave

subscription_templates_create

Create a new subscription template for Remnawave VPN clients, specifying a name and template type such as XRAY_JSON, CLASH, or SINGBOX.

Instructions

Create a new subscription template

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": {
      "name": "<name>",
      "templateType": "<templateType>"
    },
    "name": "subscription_templates_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Template name
`templateType`	Yes	Template type (client format)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Sep 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only says 'create' which implies a state change, but does not mention side effects, permissions, duplication behavior, or what happens after creation. This is a clear gap for a mutation tool.

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 concise sentence with zero wasted words. It is front-loaded with the primary action and resource, making it easy to read. Terse, but appropriately-sized for such a simple create operation.

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?

Given only two well-described parameters and no output schema, the description plus input schema is sufficient for basic invocation. However, without annotations, it lacks any note about creation behavior, defaults, or what happens after creation, leaving it at a minimum viable level but not truly complete.

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 input schema provides 100% description coverage for the two parameters (name, templateType), including an enum for templateType. The description adds no extra parameter meaning beyond the schema, 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 states the exact verb 'create' and the specific resource 'subscription template', with 'new' indicating an insert operation. This clearly distinguishes it from the other subscription_templates siblings (list, get, update, delete, reorder) without needing to open their schemas.

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?

There is no guidance on when to use this tool versus alternatives such as updating an existing template or listing templates. No prerequisites, conditions, or exclusions are mentioned, leaving the agent to infer usage purely from the tool name.

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

Deploy Server