Skip to main content
Glama

create_custom_os_template

Build custom operating system templates with specific packages and configurations for cyber range environments using ISO files from any OS.

Instructions

Create a custom OS template with specific packages and configuration.

This tool allows you to create custom Ludus templates from ANY operating system by providing an ISO URL. The OS type can be auto-detected from the ISO URL/filename, or explicitly specified. Supports Linux, Windows, BSD, macOS, and any other OS.

Args: name: Template name (e.g., "ubuntu-22.04-pentesting") os_type: OS type ("linux", "windows", "bsd", "macos") - auto-detected if None os_version: OS version (e.g., "22.04", "2022", "11") - used for default ISO lookup iso_url: Custom ISO URL (required if os_version not in defaults, supports ANY ISO) iso_checksum: Optional ISO checksum for verification (sha256) iso_checksum_type: Checksum type (default: "sha256") packages: List of packages to install (e.g., ["docker.io", "nginx", "postgresql"]) ansible_roles: List of Ansible roles to apply (e.g., ["geerlingguy.docker"]) description: Template description disk_size: Disk size (default: "40G") memory: Memory in MB (default: 4096) cores: CPU cores (default: 2) ensure_template_roles: Automatically install template roles (CommandoVM, FlareVM, REMnux) if needed auto_detect_os: Auto-detect OS type from ISO URL (default: True)

Returns: Template creation result with file paths and instructions

Example: # Create a custom Ubuntu pentesting template result = await create_custom_os_template( name="ubuntu-22.04-pentesting", os_type="linux", os_version="22.04", packages=["nmap", "metasploit-framework", "burpsuite"], description="Custom Ubuntu 22.04 with pentesting tools" )

# Create template from ANY ISO (OS auto-detected)
result = await create_custom_os_template(
    name="custom-os",
    iso_url="https://example.com/custom-linux.iso",
    iso_checksum="abc123...",
    description="Custom OS from ISO - OS type auto-detected"
)

# Create template for any operating system
result = await create_custom_os_template(
    name="arch-linux",
    iso_url="https://archlinux.org/iso/latest/archlinux-x86_64.iso",
    description="Arch Linux template"
)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
os_typeNo
os_versionNo
iso_urlNo
iso_checksumNo
iso_checksum_typeNosha256
packagesNo
ansible_rolesNo
descriptionNo
disk_sizeNo40G
memoryNo
coresNo
ensure_template_rolesNo
auto_detect_osNo
Behavior3/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 describes what the tool does (creates templates) and mentions auto-detection capabilities, but doesn't address important behavioral aspects like whether this is a long-running operation, what permissions are required, whether it's idempotent, or what happens on failure. The examples show return values but don't explain error conditions.

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 with clear sections (purpose, args, returns, examples) and front-loads the core functionality. While comprehensive, some sentences could be more concise, and the examples are quite detailed. Overall, most content earns its place by clarifying complex parameter interactions.

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 tool with 14 parameters, 0% schema coverage, and no output schema, the description does an excellent job explaining the tool's purpose, parameters, and usage through examples. The main gap is the lack of behavioral context (permissions, runtime characteristics, error handling) which would be particularly important for a template creation tool that likely involves significant processing time.

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

Parameters5/5

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

With 0% schema description coverage and 14 parameters, the description provides excellent parameter semantics. It includes an 'Args:' section explaining each parameter's purpose, default values, and usage examples. The examples demonstrate how parameters interact (e.g., iso_url vs os_version, auto_detect_os behavior), adding significant value beyond what the bare schema provides.

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 tool creates custom OS templates with specific packages and configuration, using the verb 'create' and specifying the resource 'custom OS template'. It distinguishes from sibling tools like 'create_container_template' or 'create_kali_weekly_template' by emphasizing support for ANY operating system via ISO URLs.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool (creating templates from any OS via ISO URLs) and includes examples showing different usage scenarios. However, it doesn't explicitly state when NOT to use it or mention specific alternatives among the many sibling tools, though the examples imply it's for custom OS templates rather than predefined ones.

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/tjnull/Ludus-FastMCP'

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