Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hwid_devices_list

List hardware ID devices for a specific user by supplying their numeric user ID to identify active bindings.

Instructions

List HWID devices for a specific 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>"
    },
    "name": "hwid_devices_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser numeric ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.7/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 full behavioral burden. 'List' implies a read-only operation, but the description discloses nothing about pagination, output shape, ordering, or behavior for missing users. It adds no behavioral context beyond the operation name itself.

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 front-loaded sentence with no filler, redundancy, or restating of the tool name. It is appropriately sized for a simple one-parameter list 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?

For a low-complexity single-parameter tool, the description states the essential scope, but it leaves gaps around return contents, pagination, and explicit differentiation from hwid_devices_list_all. With no output schema and no annotations, the description is minimally adequate rather than fully 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?

Schema description coverage is 100%, with userId documented as 'User numeric ID,' so the schema fully explains the only parameter. The description adds no parameter-level detail, but the baseline 3 is appropriate because the schema already covers the semantic weight.

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 uses a specific verb-resource pair ('List HWID devices') and the qualifier 'for a specific user,' which directly distinguishes it from the sibling hwid_devices_list_all. It clearly identifies both the resource and the scope of the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The qualifier 'specific user' gives clear context for when to call this tool: when you need HWID devices scoped to one user. It does not explicitly name alternatives or state when not to use it, but the sibling hwid_devices_list_all strongly implies the complementary all-devices case.

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