BC Curriculum MCP Server
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_curriculumA | Search BC curriculum (K-12) for standards, competencies, content items, and assessment resources using full-text search. Returns structured results with source metadata. Args:
Returns: Matching curriculum elements with source type, course, subject, and grade metadata. |
| get_course_curriculumA | Get the complete BC curriculum for a specific course: Big Ideas, Curricular Competencies (grouped by domain), and Content/KDU items with elaborations. Returns the full three-column structure used by BC Ministry of Education. Args:
Returns: Complete three-column curriculum structure per course, including elaborations. |
| get_grade_progressionA | Show how Big Ideas, Competencies, and Content progress across grade levels for a BC subject. Useful for understanding scaffolding, prerequisites, and learning trajectories. When a query is provided, filters to only matching items at each grade — showing a focused vertical thread rather than a full data dump. Args:
Returns: Grade-by-grade breakdown of curriculum elements showing progression, optionally filtered to a concept thread. |
| get_competency_connectionsA | Find curricular competencies that appear across multiple subjects or courses. Useful for interdisciplinary curriculum design and identifying transferable skills. Args:
Returns: Related competencies from other courses/subjects with similarity ranking. |
| list_coursesA | List all available courses in the BC curriculum database (K-12). Use this to discover what courses are available before querying specific curriculum data. Args:
Returns: List of courses with subject, grade, name, and URL. |
| search_cross_curricularA | Find curriculum elements shared between two or more subjects at the same grade level. Identifies overlapping competencies, big ideas, and content across subjects. Essential for interdisciplinary planning. Args:
Returns: Groups of curriculum items connected by shared language across subjects. |
| get_curriculum_changesA | Show what changed in BC curriculum since a given date. Detects added, removed, and modified Big Ideas, Competencies, and Content items across crawl runs. Requires at least two crawls to have change data. Args:
Returns: Course-level summary of which courses changed, plus item-level detail of what specifically was added/removed/modified. |
| get_course_historyA | Show the crawl history and change timeline for a specific course. Includes each crawl snapshot (date, item counts, content hash) and a changelog of all detected modifications. Args:
Returns: Timeline of crawl snapshots and detected changes per course. |
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 8 tools
Each tool has a clearly distinct purpose: search, get full course structure, grade progression, competency connections, course listing, cross-curricular matching, change tracking, and course history. Despite some conceptual overlap (e.g., get_competency_connections vs. search_cross_curricular), the descriptions clearly differentiate their focus (specific competencies vs. any element type).
All tool names follow a consistent snake_case verb_noun pattern: search_*, get_*, list_*. The verbs are meaningful (search, get, list) and the nouns clearly indicate the object (curriculum, course, grade, competency, etc.). No mixed conventions or ambiguous naming.
Eight tools is well-scoped for a curriculum data server. Each tool addresses a distinct query need (search, retrieval, progression, connections, listing, cross-curricular, changes, history) without redundancy or bloat. The count feels appropriate for the domain.
The tool surface covers the full range of expected queries for a curriculum server: discovery (list_courses), full-text search (search_curriculum), detailed course data (get_course_curriculum), progression analysis (get_grade_progression), interdisciplinary connections (get_competency_connections, search_cross_curricular), and change tracking (get_curriculum_changes, get_course_history). No obvious gaps for typical use cases; it's a comprehensive read-only API.