Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HEADLESSNoSet to 'true' to run the browser in headless mode. Defaults to false if not provided.
SLIIT_PASSWORDNoYour SLIIT password. Required for interactive login.
SLIIT_USERNAMENoYour SLIIT username (e.g., ITxxxxxxxx). Required for interactive login.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
list_modulesB

List all enrolled modules on SLIIT Courseweb

get_announcementsB

Get general site announcements from Courseweb

check_module_updatesC

Check for new materials or announcements in a specific module

get_deadlinesB

Fetch all upcoming assignment deadlines and events from Courseweb

scrape_pageB

Scrape the text content of any Courseweb URL to investigate the layout

download_fileC

Download a file from Courseweb (e.g. PDFs, lab sheets) given its resource URL

sync_moduleC

Bulk download all files (PDFs, lab sheets, etc.) from a specific course module

check_assignment_statusC

Check the submission status, grading status, and feedback for a specific assignment

set_session_cookieA

Manually set the MoodleSession cookie (useful for headless VMs where you can't use a browser)

interactive_loginA

Open a browser window to manually log in to SLIIT Courseweb (useful for MFA)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have distinct purposes (list_modules vs get_deadlines vs download_file vs sync_module). There is mild overlap between get_announcements (site-wide) and check_module_updates (module-specific), and between download_file (single) and sync_module (bulk), but descriptions clarify the boundaries well enough.

Naming Consistency4/5

Nearly all tools follow a consistent snake_case verb_noun pattern (list_modules, get_deadlines, check_module_updates, download_file, sync_module, check_assignment_status, set_session_cookie). Only interactive_login deviates slightly (adjective_noun) and the auth-related verbs (set/interactive) differ from the read/download verbs, but the overall style is predictable.

Tool Count5/5

Ten tools is well-scoped for a Courseweb/Moodle student client, covering listing, monitoring, downloading, assignment status, and authentication without redundancy. Each tool appears to earn its place.

Completeness4/5

The surface covers the core student lifecycle: modules, announcements, updates, deadlines, downloads, assignment status, and two complementary auth paths. Gaps remain (e.g. grades/transcript retrieval, forum/quiz access, search), but these are minor and the core workflow has no dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues