Skip to main content
Glama
moimran

EVE-NG MCP Server

by moimran

disconnect_eveng_server

Close the connection to the EVE-NG network emulation server and clean up active sessions to free resources and ensure proper session management.

Instructions

    Disconnect from EVE-NG server.
    
    This tool closes the connection to the EVE-NG server and cleans up
    any active sessions.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'disconnect_eveng_server' tool. It is decorated with @mcp.tool() for automatic registration. Disconnects the EVE-NG client and returns a success or warning message.
    @mcp.tool()
    async def disconnect_eveng_server() -> list[TextContent]:
        """
        Disconnect from EVE-NG server.
        
        This tool closes the connection to the EVE-NG server and cleans up
        any active sessions.
        """
        try:
            logger.info("Disconnecting from EVE-NG server")
            await eveng_client.disconnect()
            
            return [TextContent(
                type="text",
                text="Successfully disconnected from EVE-NG server."
            )]
            
        except Exception as e:
            logger.error(f"Error during disconnect: {e}")
            return [TextContent(
                type="text",
                text=f"Warning: Error during disconnect: {str(e)}\n\n"
                     f"Connection may have been closed already."
            )]
  • Top-level registration function that calls register_connection_tools, which in turn registers the disconnect_eveng_server handler.
    def register_tools(mcp: "FastMCP", eveng_client: "EVENGClientWrapper") -> None:
        """Register all MCP tools."""
    
        # Connection management tools
        register_connection_tools(mcp, eveng_client)
    
        # Lab management tools
        register_lab_tools(mcp, eveng_client)
    
        # Node management tools
        register_node_tools(mcp, eveng_client)
    
        # Network management tools
        register_network_tools(mcp, eveng_client)
  • The call to register_tools in the main server initialization, which ultimately registers all tools including disconnect_eveng_server.
    register_tools(self.mcp, self.eveng_client)
Behavior4/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 effectively describes the tool's behavior: closing the connection and cleaning up active sessions, which implies it is a destructive/mutation operation that ends ongoing interactions. However, it does not detail potential side effects like loss of unsaved data or error handling, leaving some behavioral aspects unspecified.

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 action in the first sentence and adds necessary detail in the second. Both sentences earn their place by clarifying the purpose and behavioral impact, with zero wasted words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 disconnect action with no parameters) and lack of annotations/output schema, the description is mostly complete. It explains what the tool does and its behavioral impact, but could improve by mentioning prerequisites (e.g., requires an active connection) or confirming it has no return values, though this is minor for a zero-param tool.

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 appropriately does not discuss parameters, focusing instead on the tool's action. A baseline of 4 is applied as it compensates well for the lack of parameters by explaining the tool's effect.

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 specific action ('Disconnect from EVE-NG server') and resource ('EVE-NG server'), distinguishing it from sibling tools like 'connect_eveng_server' and 'test_connection'. The second sentence elaborates on what disconnection entails, making the purpose unambiguous.

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 when needing to close a connection and clean up sessions, but does not explicitly state when to use this tool versus alternatives (e.g., when to disconnect vs. keep connected, or prerequisites like needing an active connection first). It provides basic context but lacks explicit guidance on exclusions or comparisons to siblings.

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