McGill VSB 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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_coursesA | Search McGill VSB by course code, subject, title, or keywords for a published term. Bounded pages; has_more indicates additional upstream suggestions. |
| get_sectionsB | Retrieve actual McGill sections, numeric times, date ranges, source component bundles and uncertainty. Reuse returned section ids or section objects with check_conflicts. |
| check_conflictsA | Check selected section_ids against current VSB data OR pass section objects from get_sections. Times that touch do not conflict; dates and weekdays must overlap. Missing times or date bounds yields complete=false; overlaps report confirmed or possible certainty. |
| generate_schedulesB | Enumerate non-conflicting combinations using VSB component bundles. Hard constraints reject schedules; ranking.mode selects six VSB sorts or local objectives, with ordered tie_breakers. Attendance metrics use inclusive dates and report exceptional meetings. Verified and provisional counts, unknown scores, and bounded search are explicit. Legacy preferences remain soft. |
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 4 tools
Each tool occupies a distinct step in the course-planning workflow: search_courses finds courses, get_sections expands them, check_conflicts validates selections, and generate_schedules builds combinations. There is no functional overlap, and the descriptions reinforce the boundaries.
All four names follow a clean snake_case verb_noun pattern (search_courses, get_sections, check_conflicts, generate_schedules). The convention is uniform and immediately readable.
Four tools map neatly onto the search → expand → validate → generate pipeline without redundancy. The scope is tight and each tool earns its place.
The surface covers the full planning lifecycle from discovery through conflict checking to schedule generation, with sensible reuse of section objects across tools. Minor gaps exist (e.g., no explicit term-listing or saved-schedule retrieval), but agents can work around these.