Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KEENETIC_HOSTNoHostname or IP address of the Keenetic router.
KEENETIC_USERNoUsername for the router's HTTP API.
KEENETIC_PASSWORDNoPassword for the router's HTTP API.

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_system_infoA

Model, firmware version, uptime, CPU and memory load, and the list of installed KeeneticOS components. Call this first when you need to know what the router supports: the component list tells you which features exist on this device. Judge memory pressure by memoryAvailableKb, not memoryFreeKb: free excludes the page cache the kernel releases on demand, so it is always low on a healthy router.

get_config_stateA

Whether the running configuration has unsaved changes, who last changed it and when, and the state of the router fail-safe timer. Unsaved changes are lost on reboot. unsavedChanges is null when the saved checksum could not be read - treat that as unknown, not as saved.

list_devicesA

Every device the router knows about, with IP, name, how it is connected, signal strength and traffic counters. Use filter to narrow to active, wired, wireless or blocked devices, and sort to rank by traffic, name, signal or last seen.

get_deviceA

Every field the router holds for a single device: DHCP lease, Wi-Fi rate and mode, access policy, traffic shaping, first and last seen. Identify it by MAC, IP or name.

update_deviceA

Rename a device, allow or block its internet access, put it on a routing policy or a schedule, or set its traffic priority. Changes apply immediately but are NOT saved: a reboot discards them until save_config is called.

list_interfacesB

Every interface on the router - WAN links, bridges, Wi-Fi access points and VPN tunnels - with link state, address and whether it carries the default route. Summary detail is the default because the full listing is very large.

get_interfaceA

Every field for a single interface, including protocol-specific detail such as WireGuard peers or PPPoE session state. Get the exact name from list_interfaces first.

set_interface_stateA

Enables or disables a network interface. Taking down a bridge or the WAN link can cut off access to the router itself, including this connection. Confirm what the interface carries with get_interface before calling this.

get_internet_statusA

Whether the router currently reaches the internet, and which check failed if not: gateway reachability, DNS resolution, and captive-portal detection. Start here when the user reports the internet is down.

list_routesA

The routing table: destination, gateway, outgoing interface and metric. Use kind=default to see only the default route, which tells you which link traffic leaves through.

list_policiesA

Connection policies, which decide that a given device leaves through a given link - typically used to send some devices through a VPN tunnel and the rest direct. The names returned here are what a device is assigned to.

get_wifi_statusA

Wi-Fi radios grouped by band, each with its access points, SSIDs, link state and the number of connected clients. Use this rather than list_interfaces when the question is about Wi-Fi coverage or which network a device should be on.

pingB

Send ICMP echo requests to a hostname or IPv4 address through the router. Supports a configurable packet count and source interface, and returns the collected ping output.

tracerouteA

Trace the network path to a hostname or IPv4 address using ICMP probes. Supports selecting the source interface, source IPv4 address, and maximum number of hops (default: 30). Returns the collected hop-by-hop traceroute output.

list_segmentsA

Every bridge on the router, and whether the web interface lists it as a segment. A bridge that carries an address but has no VLAN behind it works for traffic and never appears under /access-points, so uiVisible is the field that matters.

create_segmentA

Creates an isolated network that the web interface actually lists as a segment: a VLAN subinterface trunked over every switch port, a bridge, an address, NAT, a DHCP pool, and optionally a Wi-Fi network and a routing policy. Free identifiers are chosen automatically. The result is verified against the router-computed iseg block, and a failure anywhere rolls the whole thing back. Nothing is saved; call save_config once the user confirms.

delete_segmentA

Removes a segment and everything created with it: the Wi-Fi networks bound to it, its policy, its DHCP pool, NAT, the bridge, and the VLAN on every switch port. Removing the bridge alone leaves the VLAN trunked over the whole switch. Devices on the segment lose their connection. Refuses the home segment.

backup_configA

Saves the router startup configuration into this tool's backups directory (KEENETIC_STATE_DIR/backups) with owner-only file permissions. Take one before any sequence of changes so there is a known-good state to return to. Reading the configuration changes nothing on the router.

save_configA

Writes the running configuration to the startup configuration, so pending changes survive a reboot. Nothing else in this server saves, so call this only once the user has confirmed the changes are what they want.

rci_callA

Sends a raw request to the router RCI interface, for anything the other tools do not cover. GET reads a path such as "show/version" or "interface/Bridge0"; POST sends a command object mirroring the CLI tree. The response is capped, so ask for a narrow path rather than a broad one: show/ip/nat alone is over 100 KB.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 20 tools

Disambiguation5/5

Each tool has a distinct resource+action target (routes vs policies vs segments vs interfaces vs devices), and the descriptions explicitly resolve the few naturally overlapping cases — e.g. 'use get_wifi_status rather than list_interfaces', 'uiVisible is the field that matters' for list_segments, and rci_call is documented as the deliberate fallback for everything else. The list_/get_ pairings (list_devices/get_device, list_interfaces/get_interface) are unambiguous summary-vs-detail splits rather than duplicates.

Naming Consistency4/5

The dominant convention is verb_noun snake_case (get_system_info, list_segments, create_segment, delete_segment, update_device, save_config, backup_config) and it is applied consistently. Minor deviations exist: set_interface_state uses 'set_' where update_device uses 'update_', and ping/traceroute/rci_call are bare verbs or single tokens, though these read naturally as conventional command names.

Tool Count4/5

20 tools is on the heavy side of the 3-15 sweet spot, but for a router administration surface spanning system, routing, Wi-Fi, segments, devices, interfaces, diagnostics and config persistence, each tool maps to a real capability and none looks like filler. Slightly over-scoped rather than bloated.

Completeness4/5

Strong lifecycle coverage for segments (create/list/delete with rollback and verification) plus a coherent config-safety story (backup_config, save_config, get_config_state) and network diagnostics. Gaps remain: no direct Wi-Fi/SSID credential editing, no interface or tunnel creation, no policy creation, and no reboot/firmware tool — all reachable only via raw rci_call, which is a workable but less safe escape hatch.

Maintenance

ActivityMaintained
ResponsivenessLimited data