Skip to main content
Glama
batteryshark

System Information MCP Server

by batteryshark

get_display_info

Retrieve detailed information about connected displays including resolution, refresh rate, HDR status, and connection types for troubleshooting and multi-monitor setup verification.

Instructions

Get connected display information - resolution, refresh rate, HDR status.

Shows details for all connected monitors including resolution, refresh rates, connection types, and HDR capabilities. Essential for display troubleshooting and multi-monitor setup verification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler decorated with @mcp.tool. Imports and calls the collectors.get_display_info helper, formats output with timestamp and error handling, returns ToolResult.
    @mcp.tool
    def get_display_info() -> ToolResult:
        """Get connected display information - resolution, refresh rate, HDR status.
        
        Shows details for all connected monitors including resolution, refresh rates,
        connection types, and HDR capabilities. Essential for display troubleshooting
        and multi-monitor setup verification.
        """
        info_sections = []
        info_sections.append("# Display Information")
        info_sections.append(f"*Generated: {datetime.now().strftime('%Y-%m-%d %H:%M:%S')}*\n")
        
        try:
            from .collectors import get_display_info as get_display_data
            info_sections.extend(get_display_data())
        except Exception as e:
            info_sections.append(f"⚠️ **Display detection error**: {str(e)}")
        
        return text_response("\n".join(info_sections))
  • Main helper function collecting display information using platform-specific methods (_get_macos_displays, _get_linux_displays, _get_windows_displays). Returns formatted list of strings with display details.
    def get_display_info() -> List[str]:
        """Get display/monitor information - resolution, refresh rate, HDR status"""
        info = []
        info.append("## 🖥️ Display Information")
        
        try:
            if platform.system() == "Darwin":
                # macOS display detection
                displays = _get_macos_displays()
                if displays:
                    for i, display in enumerate(displays, 1):
                        info.append(f"\n### Display {i}")
                        for key, value in display.items():
                            info.append(f"- **{key}**: {value}")
                else:
                    info.append("- **Status**: No displays detected")
                    
            elif platform.system() == "Linux":
                # Linux display detection
                displays = _get_linux_displays()
                if displays:
                    for i, display in enumerate(displays, 1):
                        info.append(f"\n### Display {i}")
                        for key, value in display.items():
                            info.append(f"- **{key}**: {value}")
                else:
                    info.append("- **Status**: No displays detected")
                    
            elif platform.system() == "Windows":
                # Windows display detection
                displays = _get_windows_displays()
                if displays:
                    for i, display in enumerate(displays, 1):
                        info.append(f"\n### Display {i}")
                        for key, value in display.items():
                            info.append(f"- **{key}**: {value}")
                else:
                    info.append("- **Status**: No displays detected")
            else:
                info.append("- **Status**: Display detection not supported on this platform")
                
        except Exception as e:
            info.append(f"⚠️ **Display detection error**: {str(e)}")
        
        return info
Behavior2/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 describes what information is returned (resolution, refresh rates, etc.) but lacks details on permissions needed, rate limits, error conditions, or whether it's a read-only operation. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loaded with the core purpose in the first sentence, followed by elaboration in a second sentence, and ends with a concise usage context. Every sentence adds value without waste, making it efficient and well-structured for quick comprehension.

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 complexity (simple read operation with 0 parameters) and lack of annotations/output schema, the description is adequate but incomplete. It covers what data is returned but doesn't address behavioral aspects like permissions or errors. For a tool with no structured data support, it meets minimum viability but has clear gaps in providing a full context.

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, and schema description coverage is 100%, so there are no parameters to document. The description appropriately focuses on output semantics without redundant parameter info. A baseline of 4 is applied since no parameters exist, and the description adds value by explaining what data is retrieved.

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 with specific verbs ('Get connected display information') and resources ('resolution, refresh rate, HDR status'), distinguishing it from siblings like get_connected_devices or get_hardware_details by focusing exclusively on display attributes. However, it doesn't explicitly differentiate from all siblings (e.g., get_system_summary might include display info), preventing a perfect score.

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

Usage Guidelines3/5

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

The description implies usage context ('Essential for display troubleshooting and multi-monitor setup verification'), suggesting when to use it, but lacks explicit guidance on when not to use it or alternatives (e.g., vs. get_connected_devices for broader device info). It provides some direction but falls short of naming specific alternatives or exclusions.

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