Canvas Assignment Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANVAS_DOMAIN | Yes | Your Canvas institution's domain (e.g., canvas.youruniversity.edu) | |
| CANVAS_API_TOKEN | Yes | Your Canvas API access token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_coursesB | Lists all courses you are enrolled in, with options to filter by active, completed, or all courses. |
| canvas_list_active_coursesA | Lists only your active/current courses using the dashboard API. Much faster than list_courses. |
| search_assignmentsC | Searches for assignments across all courses based on title, description, due dates, and course filters. |
| get_assignmentA | Retrieves detailed information about a specific assignment, including its description, submission requirements, and embedded links. |
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 has a clearly distinct purpose: canvas_list_active_courses and list_courses both list courses but differ in scope (active-only vs. all with filters), get_assignment retrieves specific assignment details, and search_assignments searches across assignments. No overlap or ambiguity exists between these functions.
The naming is mostly consistent with a verb_noun pattern (list_courses, get_assignment, search_assignments), but canvas_list_active_courses deviates by including a domain prefix and using snake_case inconsistently. This minor inconsistency slightly reduces predictability.
With 4 tools, the server is well-scoped for its purpose of assisting with Canvas assignments. Each tool earns its place by covering core operations: listing courses, retrieving assignments, and searching assignments, without being overly sparse or bloated.
The toolset covers key read operations for courses and assignments, but there are notable gaps in write operations (e.g., creating or submitting assignments) and lifecycle management (e.g., updating or deleting assignments). Agents can work around this for query tasks but may fail for broader assignment workflows.