Skip to main content
Glama
TrackLine
by TrackLine

hwid_devices_list

Retrieve hardware ID devices associated with a specific user to manage VPN access and device authorization.

Instructions

List HWID devices for a specific user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userUuidYesUser UUID

Implementation Reference

  • The handler logic for 'hwid_devices_list' that calls 'client.getUserHwidDevices'.
    async ({ userUuid }) => {
        try {
            const result = await client.getUserHwidDevices(userUuid);
            return toolResult(result);
        } catch (e) {
            return toolError(e);
        }
    },
  • Registration of the 'hwid_devices_list' tool within the McpServer.
    server.tool(
        'hwid_devices_list',
        'List HWID devices for a specific user',
        {
            userUuid: z.string().describe('User UUID'),
        },
  • The API client helper function that performs the actual network request to list HWID devices.
    async getUserHwidDevices(userUuid: string) {
        return this.get(REST_API.HWID.GET_USER_HWID_DEVICES(userUuid));
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a list operation, implying read-only behavior, but doesn't cover aspects like pagination, rate limits, authentication needs, or what happens if the userUuid is invalid. This is a significant gap for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, fields included) or address potential errors, which is crucial for a tool with no structured output documentation. This leaves significant gaps for agent understanding.

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 schema description coverage is 100%, with the single parameter 'userUuid' fully documented in the schema. The description adds no additional parameter details beyond implying the userUuid is required for filtering. This meets the baseline of 3 when the schema does the heavy lifting.

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?

The description clearly states the action ('List') and resource ('HWID devices') with a specific scope ('for a specific user'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'hwid_device_delete' or 'hwid_devices_delete_all' beyond the list vs. delete distinction, which is why it's not a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, exclusions, or compare it to other list tools like 'users_list' or 'hosts_list', leaving the agent to infer usage from context alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TrackLine/mcp-remnawave'

If you have feedback or need assistance with the MCP directory API, please join our Discord server