Skip to main content
Glama
moimran

EVE-NG MCP Server

by moimran

get_server_info

Retrieve EVE-NG server details including version, status, capabilities, and system information to monitor and manage network emulation environments.

Instructions

    Get EVE-NG server information and status.
    
    This tool retrieves detailed information about the EVE-NG server
    including version, status, capabilities, and system information.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_server_info tool handler function, decorated with @mcp.tool(), that retrieves EVE-NG server status and formats it for display.
    @mcp.tool()
    async def get_server_info() -> list[TextContent]:
        """
        Get EVE-NG server information and status.
        
        This tool retrieves detailed information about the EVE-NG server
        including version, status, capabilities, and system information.
        """
        try:
            logger.info("Retrieving EVE-NG server information")
            
            if not eveng_client.is_connected:
                return [TextContent(
                    type="text",
                    text="Not connected to EVE-NG server. Use connect_eveng_server tool first."
                )]
            
            # Get server status and information
            status = await eveng_client.get_server_status()
            
            # Format the information nicely
            info_text = "EVE-NG Server Information:\n\n"
            info_text += f"Server URL: {eveng_client.config.eveng.base_url}\n"
            info_text += f"Version: {status.get('version', 'Unknown')}\n"
            info_text += f"Status: {status.get('status', 'Unknown')}\n"
            info_text += f"Uptime: {status.get('uptime', 'Unknown')}\n"
            
            if 'cpu' in status:
                info_text += f"CPU Usage: {status['cpu']}%\n"
            if 'memory' in status:
                info_text += f"Memory Usage: {status['memory']}%\n"
            if 'disk' in status:
                info_text += f"Disk Usage: {status['disk']}%\n"
            
            return [TextContent(
                type="text",
                text=info_text
            )]
            
        except Exception as e:
            logger.error(f"Failed to get server info: {e}")
            return [TextContent(
                type="text",
                text=f"Failed to get server information: {str(e)}"
            )]
  • Registration of connection tools (including get_server_info) by calling register_connection_tools within the overall register_tools function.
    # Connection management tools
    register_connection_tools(mcp, eveng_client)
  • Top-level registration of all tools (including get_server_info) during server component initialization.
    # Register tools
    register_tools(self.mcp, self.eveng_client)
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. It states the tool 'retrieves' information, implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or response format. This is a significant gap for a tool with zero 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and concise, with two sentences that efficiently convey the tool's purpose and details. It avoids redundancy and is front-loaded, though minor trimming (e.g., 'detailed information' could be more precise) prevents a perfect score.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is incomplete. It lacks information on behavioral aspects like authentication, error cases, or return value structure, which are crucial for an agent to use it effectively in a server management 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned any implicit context (e.g., server connection). Baseline is 4 since no parameters exist.

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 the verb 'retrieves' and resource 'EVE-NG server information and status', specifying details like version, status, capabilities, and system information. However, it doesn't explicitly differentiate from sibling tools like 'test_connection' or 'get_lab_details', which reduces it from 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 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 (e.g., server connectivity), exclusions, or comparisons to siblings like 'test_connection' for basic connectivity checks, leaving the agent to infer usage context.

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/moimran/eveng-mcp'

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