MIREA Lecture Assistant MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Read application version and scanner state without logging in or submitting anything. |
| get_settingsA | Read non-secret settings and their validation schema. No credentials or email codes. |
| get_scheduleA | Read cached schedule, without refreshing websites or opening lectures. |
| get_subject_rulesB | Read AUTO/ASK/IGNORE rules for subjects in the cached schedule. |
| update_settingsA | Apply only settings listed by get_settings. Requires explicit app-side write permission and no unsaved UI edits. Ask the user first. Changes take effect in the running app. |
| set_subject_ruleA | Set AUTO/ASK/IGNORE for an existing subject, only at user's request and with app-side permission. AUTO affects future lecture opening; never change attendance rules silently. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a primarily distinct purpose: reads cover status, settings, schedule, and subject rules, while writes cover settings and subject rules. There is minor overlap between update_settings and set_subject_rule because both modify application configuration, but the descriptions clarify the boundaries.
The set uses consistent snake_case and a predictable get_ prefix for read operations. Minor deviations exist in write verbs (update_settings vs set_subject_rule) and number agreement (get_subject_rules vs set_subject_rule), but the overall pattern remains readable.
Six tools is well-scoped for the server's purpose of reading app status/configuration and managing settings and subject rules. No tool appears redundant, and the surface is neither thin nor bloated.
The read and configuration-write surface is mostly covered, but there is no way to refresh the schedule cache or trigger lecture-opening actions mentioned in the domain. Subject rules can only be set for existing subjects, with no broader subject lifecycle management.