Skip to main content
Glama
JackXuyi

Current operating environment

getUsbInfo

Retrieve USB device information from the current operating environment to identify connected hardware and troubleshoot connectivity issues.

Instructions

获取当前设备的 USB 设备信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the getUsbInfo tool. It calls si.usb() from the systeminformation library to fetch USB information and returns it as a JSON string in the tool response format.
    case "getUsbInfo": {
      const usbInfo = await si.usb();
      return {
        content: [{
          type: "text",
          text: JSON.stringify(usbInfo, null, 2)
        }]
      };
    }
  • src/index.ts:235-243 (registration)
    Registration of the getUsbInfo tool in the tools list returned by handleRequest, including name, description, and empty input schema.
    {
      name: "getUsbInfo",
      description: "获取当前设备的 USB 设备信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema for getUsbInfo tool, which is an empty object (no parameters required).
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
  • Import of the systeminformation library (si), used by getUsbInfo and other tools to fetch USB info.
    import si from 'systeminformation'; // 导入 systeminformation 库
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it retrieves information (implying read-only), but doesn't disclose behavioral traits like whether it requires permissions, returns real-time vs cached data, format of returned info, or potential errors. For a system info tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 in Chinese that directly states the tool's function without unnecessary words. It's appropriately sized for a simple, parameterless tool and front-loads the core purpose immediately.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally complete. It tells what the tool does but lacks context about return format, data scope, or system dependencies. For a system information tool, more detail about what 'USB device information' includes would be helpful, but the basic purpose is covered.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to explain parameters, and appropriately doesn't mention any. It focuses solely on what the tool does, which is sufficient given the parameterless design.

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 tool's purpose: '获取当前设备的 USB 设备信息' (Get current device's USB device information). It specifies the verb ('获取' - get) and resource ('USB 设备信息' - USB device information), but doesn't differentiate from sibling tools like getHardwareInfo or getGraphicsInfo that also retrieve hardware information. The purpose is clear but lacks sibling 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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like getHardwareInfo (which might include USB info) and getBluetoothInfo (similar peripheral info), there's no indication of scope boundaries, prerequisites, or comparison. The agent must infer usage from the name 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/JackXuyi/env-mcp'

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