Skip to main content
Glama
Sign In
remnawave-mcp

remnawave-mcp

by 3APA3A-3AHO3A
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_host

Read-only

Retrieve a specific host by UUID from a Remnawave panel, enabling read-only inspection of host configuration and status.

Instructions

Get a host by UUID [READ] GET /api/hosts/: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_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/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, so the safety profile is covered. The description adds the HTTP verb and endpoint path ('GET /api/hosts/:uuid'), which confirms the read nature but discloses nothing about lookup behavior such as what happens on a missing UUID.

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?

Two short lines, front-loaded with purpose and zero filler. The endpoint line is arguably redundant with the annotations but no more than one line wasted.

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?

A simple single-parameter read tool with no output schema and annotations covering safety, so the burden is light. Still, the description never says what a 'host' is or what an absent/not-found UUID yields, which an agent would benefit from knowing.

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 0%, but the single uuid parameter is heavily constrained in the schema itself (uuid format plus regex pattern). The description's 'by UUID' only maps the parameter to the purpose and adds no format or sourcing detail beyond the schema.

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 a host by UUID'), which distinguishes it from the list sibling get_hosts by implying single-item lookup. However, it does not explicitly name get_hosts as the alternative, so an agent must infer the singular/plural distinction.

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 alternatives. The only hint is the implicit 'by UUID' lookup semantics, leaving the agent to infer that get_hosts is the plural counterpart.

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