GatorPath
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.
SF State degree-planning tools for the 2024-25, 2025-26, 2026-27 Bulletins: requirements follow the student's catalog year, courses and prereqs are the newest (2026-27). Answers come only from the Bulletin and reviewed rules: don't add courses, prereqs or requirements the tools didn't return. Cite the source/source_page each answer comes with (Bulletin pages; a few office policies cite that office's page), show every warning, and remind the student that the DPR and an academic advisor are the official sources for degree requirements. A course meets a GE, SF State Studies or American Institutions area only where a tool shows it (ge_areas, counted, major_courses): never infer one from a course's subject or title. Never guess what transfer credit covers (the DPR shows it), what's left or whether a student is done (audit_progress says, from the courses they typed), or when they will graduate (build_plan says). To plan a degree without the plan_my_degree prompt, call get_planning_steps first and follow it: a typed course list is enough to plan from, so don't hold the plan back for a DPR. After a plan passes check_plan, show its first term's sections (class number, days, times, room, instructor, seats) with get_sections when that term's schedule is out. Build the profile from the student's words, in full from the first call: every course with its grade exactly as given (W, I, D and F rows too), the math placement, everything in progress, advisor approvals. Don't fill in what they didn't say. first_time means they began college at SF State, not that this is their first term: set it only when they say so (false for a transfer student). Student profiles are passed in per call and never stored, except by save_profile: one file on the student's machine, only when they ask.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_coursesB | Keyword search over Bulletin course codes, titles and descriptions. |
| get_courseA | Full Bulletin record for one course: description, units, grading, GE areas, prereq (raw text + parsed tree +
status), paired/cross-listed links, source_page, and |
| get_sectionsA | Class Search sections of courses in one term (e.g. '2027-spring'), to show after a plan for its first term once
that term's schedule is out: class number (class_nbr, what Student Center asks for), meetings (days, time,
where), mode, instructor, seats_open, waitlist_open, enrolled, and attributes (permission numbers, GE tags; Class
Search shows no capacity). rate_my_professors: {instructor: a Rate My Professors search} per named instructor, links for
the student to open (anonymous student opinion, not SF State's). |
| get_prereq_chainA | Everything that must come before a course, all the way down. |
| list_programsC | Programs GatorPath has requirement rules for. verified: a person checked them against the Bulletin; drafted: AI-drafted from the Bulletin's text and checked by program (codes, pages, word-for-word quotes, units, a test plan), not yet by a person: say so when planning with one. |
| get_program_requirementsA | A program's requirement groups (as written in its rules YAML, each with its Bulletin page) plus the university graduation requirements every bachelor's degree shares: GE areas, SF State Studies, American Institutions, GWAR, unit/residence/GPA totals. catalog_year: the student's (e.g. 'Fall 2025' or '2025-26'); default the newest. |
| get_roadmapA | The Bulletin's suggested semester-by-semester roadmap. Items are course codes or slots like {slot: GE, area: "1A", units: 3}. Without a valid variant, returns the variants to choose from (for BS CS the variant follows the student's QR pathway / math placement, or the ADT for transfer students). catalog_year: the student's (e.g. 'Fall 2025'); default the newest. |
| audit_progressA | Degree audit: per requirement group satisfied / in_progress / remaining / waived (or unparsed: a rule GatorPath
can't check, with the Bulletin's |
| check_planA | Validate a term-by-term plan. Call this before presenting any plan, fix every error, and re-check until
valid. |
| build_planA | Deterministic baseline plan to graduation, laid out on the Bulletin roadmap: each term starts from its roadmap
semester (what's done is skipped, what isn't ready carries over), then the remaining required courses by prereq
chain (critical path first, corequisites together), then slots for what's open (GE areas, senior electives, free
electives) to reach the 120 and upper-division totals. Already run through check_plan: see |
| list_eligible_electivesA | Courses that can fill one requirement group's slot (e.g. 'senior_electives', 'ge_4ud', 'sfss_esca'), with the Bulletin description, so you can pick by the student's goal. |
| ge_combinationsB | Up to 8 ways (3 when more than 5 are open) to finish the open GE, SF State Studies and American Institutions requirements that one course can fill, fewest courses first, from courses that ran in the last year where that covers them (overlaps lists every course that counts for two or more); the first is the fewest a bounded search found, not a proven minimum: one course covering several (4UD + Environmental Sustainability + Global Perspectives), two that split them, or one each. Each part says what one course covers, how many courses cover exactly that (options), and examples (ready first, then recently offered); the parts can go in different terms. courses_that_fit: per open requirement, every course the student can take for it. Pass the build_plan output as plan so planned courses count; readiness is at each requirement's slot term in it (by_term: one term for all). |
| compare_programsA | What if the student changes major to |
| save_profileA | Save the student's profile so the next session starts from it. Only when the student asks to save. |
| load_profileA | Read the profile the student saved with save_profile (default ~/.gatorpath/profile.yaml), to start a session
from it. Returns |
| import_transcriptA | Read the student's SF State unofficial transcript PDF on their own machine (Student Center → Unofficial Transcript, saved as a PDF) and return only course codes, grades, units and terms: completed, in_progress, transfer_units. Name, ID, birthdate and the PDF text never leave this tool, so the student doesn't need to attach the PDF to the chat; ask for the file's path instead. Merge the result into the profile. Transfer courses show as totals only: their requirements come from the DPR. |
| import_dprA | Read the student's Degree Progress Report on their own machine (Student Center → Degree Progress Report,
printed to PDF; click Expand All and View All on long lists first) and return a ready |
| get_planning_stepsA | The Plan my degree workflow, for a client that didn't start from the plan_my_degree prompt: call it first when a student asks to plan their degree (or what's left, or when they'll graduate), then follow its steps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_my_degree | Step-by-step workflow: profile → audit → plan → electives by goal → check_plan → pace/what-ifs → advisor. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Most tools have distinct roles: imports, auditing, planning, validation, course lookup, and profile persistence are separated by resource and action. A few boundaries are nuanced, especially audit_progress versus check_plan and build_plan versus get_roadmap, but the descriptions make the intended use clear enough.
Nearly all tools use consistent snake_case verb_noun naming such as get_course, build_plan, import_dpr, and search_courses. The main outlier is ge_combinations, which is a noun phrase rather than a verb-led name, but the overall convention is still highly readable.
Eighteen tools is slightly above the ideal compact range, but the domain is genuinely broad: importing records, auditing requirements, building and checking plans, retrieving course/program data, and managing profiles. Each tool appears to earn its place, though some consolidation might be possible.
The tool set covers the main lifecycle: importing DPRs and transcripts, auditing progress, building and validating plans, exploring programs, courses, prerequisites, sections, electives, and saving/loading profiles. Minor gaps remain around explicit manual profile editing/deletion and term/calendar discovery, but core planning workflows are covered.