Skip to main content
Glama
moimran

EVE-NG MCP Server

by moimran

delete_lab

Permanently delete a lab and all its resources from EVE-NG network emulation platform. This action cannot be undone.

Instructions

Delete a lab from EVE-NG.

This tool permanently deletes a lab and all its associated resources from the EVE-NG server. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lab_pathYes

Implementation Reference

  • The core handler function for the 'delete_lab' MCP tool. It checks connection, calls the EVE-NG client to delete the lab, and returns success or error messages.
    @mcp.tool()
    async def delete_lab(lab_path: str) -> list[TextContent]:
        """
        Delete a lab from EVE-NG.
    
        This tool permanently deletes a lab and all its associated resources
        from the EVE-NG server. This action cannot be undone.
        """
        try:
            logger.info(f"Deleting lab: {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."
                )]
    
            # Delete lab
            await eveng_client.client.delete_lab(lab_path)
    
            return [TextContent(
                type="text",
                text=f"Successfully deleted lab: {lab_path}\n\n"
                     f"⚠️  This action cannot be undone. The lab and all its "
                     f"associated resources have been permanently removed."
            )]
    
        except Exception as e:
            logger.error(f"Failed to delete lab: {e}")
            return [TextContent(
                type="text",
                text=f"Failed to delete lab: {str(e)}"
            )]
  • Pydantic schema defining the input arguments for the delete_lab tool.
    class DeleteLabArgs(BaseModel):
        """Arguments for delete_lab tool."""
        lab_path: str = Field(description="Full path to the lab to delete")
  • Registration call for lab management tools, which includes the delete_lab tool.
    register_lab_tools(mcp, eveng_client)
  • Top-level registration of all tools, including delete_lab via the tools module.
    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 communicates critical behavioral traits: the action is permanent ('permanently deletes'), irreversible ('cannot be undone'), and affects associated resources ('all its associated resources'). However, it doesn't mention potential side effects like impact on running nodes or required permissions.

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 front-loaded and concise: the first sentence states the core purpose, and the second adds critical behavioral context. Every sentence earns its place with no wasted words or redundancy.

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 destructive tool with no annotations and no output schema, the description does well on behavioral transparency but leaves gaps: it doesn't explain the parameter, potential errors, or system state requirements. Given the high-stakes nature of deletion, more context would be beneficial, though the core risk is clearly communicated.

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

Parameters3/5

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

The schema description coverage is 0%, so the description must compensate. It doesn't explain the 'lab_path' parameter at all—no format, examples, or how to obtain it. The description adds no parameter-specific information beyond what's implied by the tool name, leaving the single required parameter undocumented.

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 ('Delete') and resource ('a lab from EVE-NG'), distinguishing it from siblings like delete_lab_network or delete_node which target different resources. The verb+resource combination is precise and unambiguous.

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 like wipe_all_nodes or delete_lab_network, nor does it mention prerequisites such as needing the lab to be stopped first. It only states what the tool does, not when it should be used.

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