Skip to main content
Glama

Related Servers

Alternatives to moodle-watch

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Change tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.
      8
      433 PyPI
      23
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables local-first document versioning with content-addressable storage, word-level AST diffs, and AI-compliance auditing for LLM agents.
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for structured reflection and self-modeling over Everlog diary exports, enabling agents to query local diary evidence and maintain versioned artifacts of threads, moments, beliefs, and decisions.
      MIT

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    The tools are mostly distinct in purpose—listing courses, diffing changes, showing deadlines, searching, reading, handling, and syncing. A few overlaps exist, such as whats_new also surfacing deadline changes and pending courses, and backlog overlapping with whats_new's unhandled view, but the descriptions are explicit enough to resolve ambiguity.

    Naming Consistency3/5

    All names are lowercase and use underscores, but the convention is mixed: plural nouns (courses, deadlines), bare verbs (search, sync), and verb+noun compounds (read_document, mark_handled, set_course_policy) coexist. The names are readable but not predictable from a single pattern.

    Tool Count5/5

    Twelve tools is well-scoped for a Moodle change-watching service, covering distinct phases from course policy and syncing to change discovery, reading, history, and handling. Each tool earns its place without obvious bloat or trivial additions.

    Completeness4/5

    The core workflow is covered end-to-end: sync, see what changed, inspect course structure and content, read files, mark items handled, and set course policy. Minor workarounds exist, such as no explicit undo of a handling action, but they do not block the main use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues