Skip to main content
Glama

Related Servers

Alternatives to proxmox-aiops

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.7/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (vm_list vs vm_get vs vm_config, snapshots vs backups vs storage, node/cluster/HA/task families). The only real overlap is among the power tools (vm_stop vs vm_shutdown vs vm_reboot) and the various RCA/inventory reads (cluster_resources vs vm_list vs node_status), but the descriptions explicitly contrast these, so an agent can choose correctly.

    Naming Consistency4/5

    Strong resource-prefix scheme throughout (vm_*, ct_*, node_*, cluster_*, task_*, backup_*, pool_*, storage_*, ha_*, undo_*) with all snake_case. There are minor verb-order deviations (vm_list vs node_status, vm_backup vs backup_list) but the pattern stays predictable and readable.

    Tool Count3/5

    43 tools is well above the usual sweet spot and forces the agent to scan a large surface, though the breadth of Proxmox (VMs, CTs, nodes, cluster, storage, backups, HA, firewall, undo) means each tool maps to a real operation rather than bloat. It sits at the heavy end of appropriate.

    Completeness4/5

    Lifecycle coverage is strong: inventory, start/stop/shutdown/reboot, migrate, resize/move disk, snapshots with rollback, backup/restore, tasks, undo, plus read-only cluster/storage/HA/firewall views. Gaps exist — no VM/CT creation from scratch (clone only), backup_restore is QEMU-only, and firewall/pool tools are read-only — but agents can work around most of these.

    Maintenance

    ActivityActive
    ResponsivenessLimited data