Canvas LMS CLI and MCP server for interacting with Canvas courses, assignments, submissions, and course content
Canvas MCP server has 17 tools with consistent naming (verb_noun pattern: get_*, submit_*) and complete input schemas using Zod. All tools have descriptions (avg 65 chars, within baseline). However, descriptions are terse and lack context for LLM selection, they state WHAT but not WHEN or WHY. Output schemas are not documented; responses are JSON-stringified without field-level guidance. No error handling guidance, no parameter constraints (e.g., course_id range), and no idempotency hints for write operations. Security: credentials injected server-side (good), but no permission gates or audit trail declarations. Composition is sound, tools are single-responsibility and chainable (e.g., get_course_assignments → submit_assignment_*). Missing: pagination limits documented, output field descriptions, error recovery guidance.
Get announcements for a course (instructor-posted)
Get detailed information about a specific assignment
Get all assignments for a specific course
Get files available in a course
Get all modules for a course
Get discussion topics for a course (topic info only — no student replies)
Output schemas not documented. Responses are JSON-stringified without field-level descriptions. LLMs cannot infer which fields are IDs for chaining, which are metadata, or what types to expect. Violates pattern:tool and pattern:response-shaper.
Descriptions are terse (avg 65 chars) and lack context for LLM selection. They state WHAT (e.g., 'Get all assignments') but not WHEN to use this tool vs. similar ones or what prerequisites exist. Baseline for A+ tools is 50-200 chars with WHEN/WHY guidance.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Get all items in a specific module
Get all courses you are enrolled in
Get your own Canvas user profile information
Get your own submission for a specific assignment
Get your own submissions for all assignments in a course
Get your Canvas todo items
Get your upcoming assignments and events
Get the content of a Canvas page in a course
Upload and submit a file for an assignment. Provide the absolute path to the file on disk.
Submit a text entry for an assignment
Submit a URL for an assignment
No error handling guidance. Tools do not document what errors can occur, whether they are retryable, or what the LLM should do next. Violates pattern:recovery-guide and pattern:error-classification.
Write operations (submit_assignment_*) lack idempotency hints and confirmation/dry-run support. Agents cannot safely retry on ambiguous failures without risking duplicate submissions. Violates pattern:idempotent-operation and pattern:confirmation-request.
No pagination limits or result count caps documented. Tools like get_my_courses and get_course_assignments may return hundreds of items, exhausting context window. Baseline requires explicit limit (20-50) and pagination guidance.