Skip to main content
Glama
batteryshark

System Information MCP Server

by batteryshark

get_connected_devices

Identify and list all connected USB devices and paired Bluetooth devices to troubleshoot peripheral issues and maintain device inventory.

Instructions

Get USB and Bluetooth device information.

Lists all connected USB devices and paired/active Bluetooth devices. Useful for peripheral troubleshooting and device inventory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary tool handler for 'get_connected_devices'. Decorated with @mcp.tool for registration. Fetches device info via get_connectivity_devices() helper, formats with timestamp/header, and returns as ToolResult text content.
    @mcp.tool
    def get_connected_devices() -> ToolResult:
        """Get USB and Bluetooth device information.
        
        Lists all connected USB devices and paired/active Bluetooth devices.
        Useful for peripheral troubleshooting and device inventory.
        """
        info_sections = []
        info_sections.append("# Connected Devices")
        info_sections.append(f"*Generated: {datetime.now().strftime('%Y-%m-%d %H:%M:%S')}*\n")
        
        try:
            info_sections.extend(get_connectivity_devices())
        except Exception as e:
            info_sections.append(f"⚠️ **Device detection error**: {str(e)}")
        
        return text_response("\n".join(info_sections))
  • Core helper function implementing the device collection logic. Combines USB devices (via get_usb_devices()) and Bluetooth devices (via get_bluetooth_devices()), formats as markdown list.
    def get_connectivity_devices() -> List[str]:
        """Get USB and Bluetooth device information"""
        info = []
        info.append("## 🔌 Connected Devices")
        
        # USB devices
        usb_info = get_usb_devices()
        if len(usb_info) > 1:  # More than just the header
            info.extend(usb_info)
        
        # Bluetooth devices  
        bt_info = get_bluetooth_devices()
        if len(bt_info) > 1:  # More than just the header
            info.append("")  # Add spacing
            info.extend(bt_info)
        
        return info
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what information is returned (device information, lists of devices) and hints at the scope (connected USB, paired/active Bluetooth). However, it doesn't disclose important behavioral traits like whether this requires elevated permissions, how current the data is, what format the information comes in, or potential performance implications.

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 perfectly structured with three concise sentences that each earn their place: first states the core purpose, second elaborates on scope, third provides usage context. No wasted words, front-loaded with the essential information, and appropriately sized for a zero-parameter tool.

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 zero-parameter tool with no output schema, the description provides adequate coverage of what the tool does and when to use it. However, without annotations and with no output schema, it lacks important contextual details about the return format, data freshness, permission requirements, and error conditions that would be helpful for an AI agent to use this tool effectively.

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, so the baseline would be 3. However, the description adds value by clarifying that no filtering parameters are needed - it returns 'all connected USB devices' and 'paired/active Bluetooth devices' without requiring any input. This semantic clarification about the comprehensive nature of the output justifies a higher score.

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 clearly states the tool's purpose with specific verbs ('Get', 'Lists') and resources ('USB and Bluetooth device information', 'connected USB devices', 'paired/active Bluetooth devices'). It distinguishes itself from sibling tools by focusing specifically on peripheral devices rather than displays, networks, processes, or other system aspects.

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 description provides clear context for when to use this tool ('Useful for peripheral troubleshooting and device inventory'), which helps differentiate it from general system reporting siblings. However, it doesn't explicitly state when NOT to use it or name specific alternative tools for related but different purposes.

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/batteryshark/mcp-sysinfo'

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