Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP listen port.8329
MCP_BEARER_TOKENNoRequired in HTTP mode; not used in --stdio mode.
AUSSIEBB_PASSWORDYesMyAussie portal login password.
AUSSIEBB_SERVICESNoOptional alias=id map, e.g. home=1000001,office=1000002.
AUSSIEBB_USERNAMEYesMyAussie portal login username.
AUSSIEBB_SESSION_FILENoFile where the ~1-year login cookie persists.~/.local/state/aussiebb-mcp/session.json

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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_servicesA

List services on the AussieBB account: service_id, site alias, plan, speed tier, address, WAN IPs. service_type: 'NBN' (default) or 'all'.

list_diagnosticsB

List the diagnostics AussieBB offers for a service (name, summary, which are destructive). service: a site alias | id | 'all'.

check_connectionA

Instant ISP-side connectivity check: is the service connected from AussieBB's end? Safe, non-disruptive. THE first diagnostic to run. service: a site alias | service_id | 'all' (default).

ntd_statusA

Run an NTD Status test (~2 min): NBN box link state, uptime, and dropout ('flap') count — the evidence AussieBB's fault process keys on. Safe, non-disruptive. service: a site alias | service_id. wait=False returns immediately with a test id to poll via test_result.

loopback_testA

Run a Loopback test (~2 min): proves data passes both ways between AussieBB and the NBN box/node. Safe, non-disruptive. service: a site alias | service_id. wait=False returns immediately with a test id to poll via test_result.

test_resultA

Fetch one test's current status/result by id (from test_history or a wait=False run). service: a site alias | service_id.

test_historyC

Recent diagnostic runs (type, status, Passed/Failed, timestamps). service: a site alias | service_id | 'all' (default).

service_outagesA

Current, scheduled, and resolved NBN/AussieBB outages for the service — check this before blaming local gear. service: a site alias | service_id | 'all' (default).

speed_test_resultsB

Speed test results recorded against the service by AussieBB. service: a site alias | service_id | 'all' (default).

list_faultsC

Open fault tickets on the AussieBB account (account-wide, not per-service).

kick_connectionA

DESTRUCTIVE: drop the service's session at AussieBB (use when swapping the modem/router; reconnection can take ~10 min). Refuses unless confirm=true — get the user's explicit approval first. service: a site alias | service_id (never 'all').

ntd_resetA

DESTRUCTIVE: reboot the NBN box (minutes of outage while it restarts). Only useful when NTD Status errors. Refuses unless confirm=true — get the user's explicit approval first. service: a site alias | service_id (never 'all').

run_diagnosticA

Run any diagnostic by name ('NTD Status', 'loopback', ...) — escape hatch equivalent to the portal's Run Tests buttons. Destructive tests (kick_connection, ntd_reset) still require confirm=true. service: a site alias | service_id.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation5/5

Each tool has a distinct purpose: listing services, listing diagnostics, running specific tests, fetching results, checking history, outages, speed tests, faults, and destructive actions. Even similar diagnostics (check_connection, ntd_status, loopback_test) are clearly differentiated by their descriptions, and run_diagnostic serves as an explicit escape hatch.

Naming Consistency4/5

Most tools follow a verb_noun pattern (list_services, check_connection, run_diagnostic), but some are noun-first test names (ntd_status, loopback_test, speed_test_results). The naming is readable and generally predictable, though not perfectly uniform.

Tool Count5/5

13 tools is well-scoped for an ISP diagnostics and management server. Each tool covers a real need (service listing, connectivity checks, test execution, result retrieval, outages, faults, destructive actions), and the count is not excessive.

Completeness4/5

The server provides comprehensive diagnostic coverage, including running tests, fetching results, and viewing history, plus outages and service info. Minor gaps exist like lack of fault creation, but the presence of run_diagnostic as a catch-all and the account-wide focus mitigate these.

Maintenance

ActivitySlowing
ResponsivenessNo issues