Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
site_infoA

Moodle site info and the logged-in user (name, userid, available web-service functions).

list_coursesA

List the user's enrolled iSpace courses (id, name, progress).

course_contentsA

Sections, activities and files of a course. File URLs are token-redacted; pass them to download_file.

list_assignmentsA

List assignments (due dates in the configured timezone, default Asia/Shanghai). Omit courseids to cover all enrolled courses.

submission_statusB

Submission/grading status of one assignment (use the assignid from list_assignments).

upcoming_deadlinesA

Assignments due within the next days days, soonest first, times in the configured timezone.

download_fileA

Download an iSpace file (fileurl from course_contents / list_assignments) to dest_dir (default ~/Downloads/ispace). Returns the saved path. Only iSpace URLs are allowed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation4/5

Each tool targets a distinct resource or view: site info, courses, course contents, assignments, per-assignment submission status, upcoming deadlines, and file download. The only mild overlap is between list_assignments and upcoming_deadlines, but the descriptions clarify the latter is a filtered, time-window view.

Naming Consistency4/5

All names are snake_case and predictable, though a few read as bare nouns (site_info, course_contents, submission_status) while others use verb_noun (list_courses, download_file). Still readable and consistent enough that the pattern holds.

Tool Count5/5

Seven tools is well-scoped for a Moodle/iSpace client, with each tool earning its place across info, listing, detail, and download operations. No redundancy or bloat.

Completeness4/5

The read surface covers the core lifecycle: courses, contents, assignments, submission/grading status, deadlines, and file retrieval. Minor gaps exist (no grade overview across courses, no assignment submission/upload), but these are workable if the integration is intentionally read-focused.

Maintenance

ActivityMaintained
ResponsivenessSyncing