Skip to main content
Glama
moimran

EVE-NG MCP Server

by moimran

get_node_details

Retrieve comprehensive configuration, status, and connectivity details for a specific node in EVE-NG network labs to analyze and manage network emulation environments.

Instructions

Get detailed information about a specific node.

This tool retrieves comprehensive information about a node including its configuration, status, interfaces, and connectivity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsYes

Implementation Reference

  • The main handler function for the 'get_node_details' MCP tool. It validates input, checks EVE-NG connection, retrieves node data via eveng_client.get_node(), formats comprehensive details (status, config, position, interfaces) into TextContent, handles errors.
    @mcp.tool()
    async def get_node_details(arguments: GetNodeDetailsArgs) -> list[TextContent]:
        """
        Get detailed information about a specific node.
    
        This tool retrieves comprehensive information about a node including
        its configuration, status, interfaces, and connectivity.
        """
        try:
            logger.info(f"Getting node details: {arguments.node_id} in {arguments.lab_path}")
    
            if not eveng_client.is_connected:
                return [TextContent(
                    type="text",
                    text="Not connected to EVE-NG server. Use connect_eveng_server tool first."
                )]
    
            # Get node details
            node = await eveng_client.get_node(arguments.lab_path, arguments.node_id)
    
            if not node.get('data'):
                return [TextContent(
                    type="text",
                    text=f"Node {arguments.node_id} not found in lab {arguments.lab_path}"
                )]
    
            node_data = node['data']
            status_icon = "🟢" if node_data.get('status') == 2 else "🔴" if node_data.get('status') == 1 else "⚪"
    
            # Format node information
            details_text = f"Node Details: {node_data.get('name', f'Node {arguments.node_id}')}\n\n"
    
            details_text += f"{status_icon} Basic Information:\n"
            details_text += f"   ID: {arguments.node_id}\n"
            details_text += f"   Name: {node_data.get('name', 'Unknown')}\n"
            details_text += f"   Template: {node_data.get('template', 'Unknown')}\n"
            details_text += f"   Type: {node_data.get('type', 'Unknown')}\n"
            details_text += f"   Image: {node_data.get('image', 'Unknown')}\n"
            details_text += f"   Status: {_get_status_text(node_data.get('status', 0))}\n\n"
    
            details_text += f"⚙️  Configuration:\n"
            details_text += f"   Console: {node_data.get('console', 'Unknown')}\n"
            details_text += f"   CPU: {node_data.get('cpu', 'Unknown')}\n"
            details_text += f"   RAM: {node_data.get('ram', 'Unknown')} MB\n"
            details_text += f"   Ethernet Interfaces: {node_data.get('ethernet', 'Unknown')}\n"
            details_text += f"   Serial Interfaces: {node_data.get('serial', 'Unknown')}\n"
            details_text += f"   Delay: {node_data.get('delay', 0)} seconds\n\n"
    
            details_text += f"📍 Position:\n"
            details_text += f"   Left: {node_data.get('left', 0)}%\n"
            details_text += f"   Top: {node_data.get('top', 0)}%\n"
    
            return [TextContent(
                type="text",
                text=details_text
            )]
    
        except Exception as e:
            logger.error(f"Failed to get node details: {e}")
            return [TextContent(
                type="text",
                text=f"Failed to get node details: {str(e)}"
            )]
  • Pydantic schema defining the input arguments for the get_node_details tool: lab_path (str) and node_id (str).
    class GetNodeDetailsArgs(BaseModel):
        """Arguments for get_node_details tool."""
        lab_path: str = Field(description="Full path to the lab (e.g., /lab_name.unl)")
        node_id: str = Field(description="Node ID to get details for")
  • Registration call for node management tools within the overall register_tools function. This invokes register_node_tools which defines @mcp.tool()-decorated get_node_details handler.
    register_node_tools(mcp, eveng_client)
  • Top-level registration of all MCP tools in the server startup, calling register_tools(mcp, eveng_client) which chains to node_management registration including get_node_details.
    register_tools(self.mcp, self.eveng_client)
  • Helper utility used by get_node_details to convert numeric node status codes (0-3) to readable strings like 'Running', 'Stopped'.
    def _get_status_text(status: int) -> str:
        """Convert node status code to human-readable text."""
        status_map = {
            0: "Stopped",
            1: "Starting",
            2: "Running",
            3: "Stopping"
        }
        return status_map.get(status, f"Unknown ({status})")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'retrieves' information (implying read-only) and mentions what information is included (configuration, status, interfaces, connectivity), but doesn't cover critical aspects like authentication requirements, error handling, rate limits, or whether it requires the node to be running. The disclosure is incomplete for a tool that likely interacts with a lab environment.

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 appropriately concise with two sentences that directly address purpose and scope. The first sentence states the core function, and the second elaborates on what information is retrieved. There's no unnecessary verbiage, though it could be slightly more structured with bullet points for the information types.

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 complexity of interacting with a lab/node system, no annotations, no output schema, and poor parameter documentation, the description is insufficient. It doesn't explain what format the detailed information returns, how to interpret the configuration/status/interface data, or error conditions. For a tool that likely returns structured node data in a lab environment, more context is needed.

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

Parameters1/5

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

The description provides no information about parameters beyond the tool name implying a 'node' is needed. With 0% schema description coverage and 1 required parameter (though the schema shows 2 nested parameters: lab_path and node_id), the description fails to explain what 'arguments' should contain, what format lab_path expects, or how node_id is determined. This leaves parameters completely undocumented.

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 a specific verb ('Get') and resource ('node'), specifying it retrieves 'detailed information' about a specific node. It distinguishes from siblings like 'list_nodes' (which lists nodes) and 'get_lab_details' (which focuses on labs), but doesn't explicitly contrast with 'get_lab_topology' which might also provide node information in a network context.

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 when to choose 'get_node_details' over 'get_lab_topology' (which might include node details) or 'list_nodes' (which provides basic node information), nor does it specify prerequisites like needing an existing node or lab 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