Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ROUTER_BASE_URLYesYour explicit router root URL; no discovery or hard-coded installation address
ROUTER_PASSWORDYesRouter password
ROUTER_USERNAMEYesRouter account
ROUTER_TLS_SHA256NoIndependently verified SHA-256 leaf-certificate pin for a self-signed router
ROUTER_ALLOW_WRITESNoEnable intentional mutations/actionsfalse
ROUTER_UPNP_BASE_URLNoExplicit UPnP root URL on the same hostname; observed service port was 52869
ROUTER_ALLOW_DANGEROUS_ACTIONSNoAlso permit disruptive operations such as restart, reset, WAN termination, scans or counter resetsfalse

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

Tools

Functions exposed to the LLM to take actions

NameDescription
router_list_endpointsA

List the public source-derived endpoint catalog and verification status; no router request.

router_readB

Read a documented passive handler. Active Wi-Fi scans and all actions are excluded. Secrets are redacted.

router_get_dhcpA

Read current DHCP settings without changing them.

router_get_wifiA

Read radio settings, SSID status and associated clients. Does not start a radio scan.

router_set_dhcp_rangeA

Patch DHCP boundaries only; preserve other settings and verify by fresh read-back. Requires writes enabled and explicit user approval.

router_set_24ghz_modeA

Set the existing 20 MHz 2.4 GHz radio to b/g, b/g/n or b/g/n/ax. May briefly restart that radio. Preserve other settings and verify read-back; no 5 GHz changes.

router_execute_actionB

Expert wire-level operation from the allowlisted catalog, not a generic patch. Review endpoint fields/hooks first. Requires writes enabled and explicit approval; disruptive actions require a second opt-in. Never assume Cancel means undo.

router_soap_readB

Call an advertised read-only SOAP action. Requires explicit UPnP origin configuration; some advertised getters are known to fault.

router_soap_actionB

Explicit SOAP mutation/action. Requires UPnP configuration, writes enabled, confirmation and additional disruptive-action permission where applicable.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
endpoint-catalogSanitized public endpoint evidence and candidate schemas.

TDQS

A3.6/5.0

Scored across 9 tools

Disambiguation4/5

Most tools target clearly different resources or actions, but router_read, router_get_dhcp, router_get_wifi, and router_soap_read form a cluster of read operations that could be confused. Similarly, router_execute_action and router_soap_action are both generic write paths, though the descriptions mostly disambiguate by protocol and safety level.

Naming Consistency4/5

All tools consistently use the router_ prefix and snake_case, with mostly verb-led names such as router_list_endpoints and router_set_dhcp_range. Minor deviations include router_read as a bare verb and router_soap_read/router_soap_action placing the protocol qualifier before the action.

Tool Count5/5

Nine tools is well within the appropriate range for a router-control server. The set includes specific safe helpers plus generic read/action and SOAP paths without feeling bloated.

Completeness4/5

The set covers endpoint discovery, DHCP and Wi-Fi reads, targeted DHCP/radio writes, and generic/SOAP read-action paths, which is solid for this router wrapper. Some common operations such as broader Wi-Fi/SSID writes or 5 GHz changes are left to generic actions rather than dedicated tools.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues