Skip to main content
Glama

import_egg

Destructive

Create or import server templates (eggs) in Pterodactyl to define Docker images, startup commands, and configurations for game servers.

Instructions

Import or create a new egg (server template) in a nest (admin action). Eggs define the Docker image, startup command, and configuration for a type of game server. Use list_nests to find the nest_id first. The egg will be available for creating new servers via create_server. Requires Application API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nest_idYesNest ID to create the egg in (from list_nests)
nameYesDisplay name for the egg
descriptionNoDescription of what this egg runs
docker_imageYesDocker image to use (e.g. 'ghcr.io/image:tag')
startupYesStartup command with variable placeholders (e.g. 'java -jar {{SERVER_JARFILE}}')
config_fromNoEgg ID to inherit configuration from
config_stopNoStop command sent to the server process
config_logsNoJSON config for log parsing
config_filesNoJSON config for file parser modifications
config_startupNoJSON config for startup detection
script_containerNoDocker image for the install script (e.g. 'alpine:3.4')
script_entryNoEntrypoint for the install script (e.g. 'bash')
script_installNoShell script executed during server installation
Behavior4/5

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

Annotations provide openWorldHint=true and destructiveHint=true, indicating this creates new resources with potential side effects. The description adds valuable context beyond annotations: it clarifies this is an 'admin action' requiring specific permissions ('Requires Application API key') and explains the downstream impact ('available for creating new servers via create_server'). No contradiction with annotations.

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?

Perfectly structured with three focused sentences: first states purpose, second provides usage guidance, third specifies requirements. Every sentence adds essential information with zero wasted words. The description is appropriately sized for a complex admin tool.

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?

For a complex creation tool with 13 parameters and destructiveHint=true, the description provides excellent context about purpose, prerequisites, and downstream usage. The main gap is lack of output information (no output schema), but the description compensates well by explaining the egg's purpose and relationship to create_server.

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?

With 100% schema description coverage, the input schema already documents all 13 parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it only mentions the need for 'nest_id' from list_nests. This meets the baseline expectation when schema coverage is complete.

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 verb ('Import or create') and resource ('a new egg (server template) in a nest'), explaining that eggs define Docker images and configurations for game servers. It distinguishes from siblings like 'create_server' by specifying this is an admin action for defining server templates, not creating actual servers.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use guidance: 'Use list_nests to find the nest_id first' and 'The egg will be available for creating new servers via create_server'. It also specifies prerequisites: 'Requires Application API key', clearly differentiating this admin action from regular server operations.

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/zefarie/pterodactyl-mcp'

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