Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
--backendNoBackend to use. Use 'mock' for the default fictional in-memory fixtures, or 'live' to opt into the scoped Proxmox HTTPS adapter. Live mode also requires an HTTPS origin, one node, allowed guest IDs, and an owner-only token file; see docs/USAGE.md and .env.example.mock

Instructions

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

Read-only inventory tools. The default backend is fictional. Live scope and credentials are selected only by the host at startup. Backup metadata is not proof of a successful restore.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
node_statusA

Read status of the configured node; no infrastructure modifications.

list_guestsA

List configured-scope virtual machines and containers.

guest_configC

Read selected resource configuration of one scoped guest.

storage_statusC

Read selected storage availability and usage fields.

backup_jobsC

Read selected backup scheduling metadata.

backup_historyA

Read recent backup task metadata; this does not verify restore success.

guest_snapshotsB

Read snapshot metadata for one scoped guest.

firewallA

Inspect selected firewall rules; no rule changes are available.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a clearly distinct Proxmox resource or metadata category: node, guests, guest configuration, storage, backup schedules, backup history, snapshots, and firewall rules. The closest pair, backup_jobs and backup_history, is still clearly separated as scheduling metadata versus recent task metadata.

Naming Consistency4/5

The set is consistently snake_case and mostly uses noun-based resource labels such as node_status, storage_status, backup_jobs, and guest_snapshots. The main deviation is list_guests, which uses a verb-first pattern while the rest are noun phrases.

Tool Count5/5

Eight tools is well-scoped for a read-only Proxmox inspection server, covering the main resource areas without excessive surface area. Each tool corresponds to a meaningful read-only concern.

Completeness3/5

The server covers node, guest, storage, backup, snapshot, and firewall reads, but notable Proxmox read operations are absent, such as guest runtime status, task logs/details, network configuration, and cluster-level status. These gaps are workable for limited inspection but will cause dead ends for common read-only diagnostics.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues