Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WISP_API_TOKENYesYour WISP Client API token
WISP_PANEL_URLYesThe URL of the WISP panel (e.g., https://panel.example.com)
WISP_SERVER_IDNoOptional default server ID
WISP_ALLOW_POWERNoSet to 'true' to allow power operations (start, stop, restart)
WISP_ALLOW_BACKUPSNoSet to 'true' to allow backup operations
WISP_ALLOW_COMMANDSNoSet to 'true' to allow sending console commands
WISP_ALLOW_DATABASESNoSet to 'true' to allow database operations
WISP_ALLOW_DESTRUCTIVENoSet to 'true' to allow destructive operations (file deletion, backup restore/delete, database deletion, force-kill, panel update). Keep false during normal administration.
WISP_ALLOW_FILE_WRITESNoSet to 'true' to allow file write operations
WISP_ALLOW_SERVER_SETTINGSNoSet to 'true' to allow modifying server settings

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
capabilitiesA

Inspect which Wisp operation classes are enabled before choosing a management tool. Returns configuration flags and the default server ID, but never API tokens or other secrets.

list_serversA

List Wisp servers visible to the configured API token. Use this to discover server IDs; results are paginated and can optionally include node, egg, or allocation metadata.

server_detailsA

Read metadata for one Wisp server without changing it. Use for identity, allocation, feature, node, or egg details; omit server_id only when a default server is configured.

server_statusA

Read the current runtime state and resource usage for one server. Use for power state, CPU, memory, disk, network, and game-query checks; this performs no mutation.

audit_logsA

Read one page of Wisp audit events for a server. Use to investigate recent panel actions or changes; page and per_page control pagination and no state is modified.

list_directoryA

List entries in one server directory without reading file contents. Use for filesystem discovery before read or write operations; results are paginated.

read_fileA

Read a text file and return its content plus fingerprint metadata. Use when the full file is needed; content is truncated at max_chars, so use read_file_chunk for controlled continuation.

file_fingerprintA

Return SHA-256 and size metadata for a text file without returning its content. Use before safe_write_file or replace_in_file when only concurrency verification is needed.

read_file_chunkA

Read a bounded character slice of a text file and return continuation metadata plus the whole-file SHA-256. Use for large files when full context is unnecessary; continue with next_offset_chars.

find_in_fileA

Find literal text in a server file and return bounded, line-numbered excerpts. Use to locate relevant sections before chunked reading or exact replacement; this is not regex search and makes no changes.

read_log_tailA

Return the last requested lines from a text log file. Use for recent diagnostics after commands, power actions, or edits; it reads the file without modifying it.

create_directoryA

Create a directory in the server filesystem. Use only when a new directory is required; this mutates filesystem state and requires WISP_ALLOW_FILE_WRITES.

write_fileA

Create or fully overwrite a text file. Use for new files or deliberate full replacement; it mutates filesystem state, requires WISP_ALLOW_FILE_WRITES, and does not protect against concurrent edits.

safe_write_fileA

Overwrite an existing text file only when its current SHA-256 matches expected_sha256, then verify the stored result. Prefer this over write_file for existing files; requires WISP_ALLOW_FILE_WRITES.

replace_in_fileA

Replace an exact text snippet only when the file SHA-256 and match count are exactly as expected, then verify the result. Prefer for small edits to existing files; requires WISP_ALLOW_FILE_WRITES.

copy_fileA

Ask Wisp to copy a file in place. Use to create a safety copy before risky edits when supported by the panel; this writes filesystem state and requires WISP_ALLOW_FILE_WRITES.

rename_fileA

Rename or move a server file to a new path. Use only when the existing path should change; this mutates filesystem state and requires WISP_ALLOW_FILE_WRITES.

compress_filesA

Create an archive from up to 100 server paths. Use for packaging or pre-change snapshots; this creates a new filesystem object and requires WISP_ALLOW_FILE_WRITES.

decompress_archiveA

Extract an archive in the server filesystem. Use only when archive contents should be written to disk; existing paths may be affected and WISP_ALLOW_FILE_WRITES is required.

delete_fileA

Permanently delete a server file. Use only for an explicit deletion request; this is destructive and requires both WISP_ALLOW_FILE_WRITES and WISP_ALLOW_DESTRUCTIVE.

send_console_commandA

Execute one command in the game-server console. Use for explicit runtime administration commands; effects depend on the command and WISP_ALLOW_COMMANDS must be enabled.

powerA

Change a server power state with start, stop, restart, or force-kill. Use only when a power action is intended; WISP_ALLOW_POWER is required and kill also requires WISP_ALLOW_DESTRUCTIVE.

list_backupsA

List one page of backups for a server without modifying them. Use to discover backup IDs, names, state, and metadata before restore, delete, lock, or download operations.

create_backupA

Create a named server backup. Use before risky changes or when a new recovery point is required; this creates panel state and requires WISP_ALLOW_BACKUPS.

deploy_backupA

Restore a server from an existing backup ID. Use only for an explicit restore request because current server data can be replaced; requires WISP_ALLOW_BACKUPS and WISP_ALLOW_DESTRUCTIVE.

delete_backupA

Permanently delete a backup by ID. Use only for an explicit backup deletion request; requires WISP_ALLOW_BACKUPS and WISP_ALLOW_DESTRUCTIVE.

lock_backupA

Change the panel lock state for a backup ID. Use to protect a backup from accidental deletion when supported; requires WISP_ALLOW_BACKUPS and mutates backup state.

backup_downloadB

Request Wisp download metadata for a backup without changing it. Use when a client needs the panel-provided backup download response for an existing backup ID.

list_databasesA

List one page of databases attached to a server. Use to discover database IDs and optionally host metadata; this is read-only and page/per_page control pagination.

create_databaseA

Create a database allocation for a server through the Wisp Client API. Use only when a new database is requested; this changes panel state and requires WISP_ALLOW_DATABASES.

rotate_database_passwordA

Generate a new password for an existing database. Use only for an explicit credential rotation because the old password stops working; requires WISP_ALLOW_DATABASES and WISP_ALLOW_DESTRUCTIVE.

delete_databaseA

Permanently delete a database allocation by ID. Use only for an explicit deletion request; this is destructive and requires WISP_ALLOW_DATABASES and WISP_ALLOW_DESTRUCTIVE.

toggle_monitoringA

Switch Wisp monitoring to its opposite state for the selected server. Each call flips the current setting, so do not retry blindly. Requires WISP_ALLOW_SERVER_SETTINGS.

toggle_support_accessA

Switch hosting-provider support access to its opposite state. Each call flips the current setting, so do not retry blindly. Requires WISP_ALLOW_SERVER_SETTINGS.

update_serverA

Run the Wisp egg update action for the selected server, optionally using the beta channel. Use only for an explicit update request; this can change server files/runtime and requires server-settings plus destructive access.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 35 tools

Disambiguation4/5

Most tools target distinct resources and actions, and descriptions clarify the intended use. The main overlap is among file-reading tools (read_file, read_file_chunk, find_in_file, file_fingerprint) and write variants (write_file, safe_write_file, replace_in_file), but these are differentiated by context and safety requirements.

Naming Consistency4/5

The set predominantly follows a snake_case action-prefix convention such as list_servers, read_file, create_backup, and delete_database. Minor deviations appear in noun-style tools like capabilities, server_details, server_status, audit_logs, file_fingerprint, power, and backup_download, but the casing remains consistent and readable.

Tool Count3/5

The 35 tools cover several substantial subdomains: servers, files, backups, databases, console/power, and settings. This breadth makes the count defensible, but it is still heavy and may overwhelm agents selecting among many related file and backup operations.

Completeness4/5

Coverage is broad across server inspection, power/console control, filesystem operations, backups, databases, and settings. Gaps remain for possible panel operations such as scheduled tasks, user/subuser management, allocation management, startup variable editing, or explicit file upload/download, but core lifecycle workflows are well covered.

Maintenance

ActivityNo data
ResponsivenessSyncing