Skip to main content
Glama
Sign In
remnawave-mcp

remnawave-mcp

by 3APA3A-3AHO3A
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_subscription_template

Read-only

Retrieve a Remnawave subscription template by UUID to inspect its configuration details in chat.

Instructions

Get subscription template by uuid [READ] GET /api/subscription-templates/:uuid

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": "get_subscription_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the '[READ] GET /api/...' line merely restates that safety profile plus the endpoint path. No additional behavior is disclosed (e.g., behavior on unknown uuid, permissions, or template contents).

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?

Front-loaded and brief with no filler prose. The bracketed '[READ] GET /api/...' fragment is largely redundant with the annotations, so it does not fully earn its place.

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 single-param read with annotations covering safety and no output schema, the definition is minimally adequate. It omits any description of what a subscription template is, edge-case behavior, or routing relative to the list sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single uuid parameter has 0% schema description coverage, so the description carries the burden, but 'by uuid' adds only the bare minimum. It does not state whether the uuid refers to a template id, a version, or what happens if it is malformed or not found.

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?

States a specific verb and resource ('Get subscription template by uuid'), which is clear enough to identify the operation. It does not explicitly differentiate from the sibling get_subscription_templates (list-all), though the 'by uuid' qualifier implies single-item retrieval.

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 when-to-use guidance, no prerequisites, and no mention of the natural alternative get_subscription_templates. The agent must infer that this tool retrieves one template given its uuid rather than the full list.

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