Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Courses

list_courses
Read-only

Retrieve Canvas courses for the authenticated user, using slim mode for quick selection or full mode with extra fields; filter by workflow state, enrollment state, or exclude blueprints.

Instructions

List courses for the authenticated user. Use fields="slim" when enumerating courses for selection; switch to "full" once you have identified the target. slim returns id, name, course_code, term name, and workflow_state only. "full" (default) includes all Canvas fields plus include extras (teachers, total_students, syllabus_body, etc.). state[] narrows by course workflow state; enrollment_state narrows by the caller's enrollment state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoFilter by course workflow state
fieldsNoProjection mode: "slim" returns id/name/course_code/term/workflow_state only; "full" (default) returns all fields
includeNoExtra fields to include on each course (Canvas include[] param); ignored when fields="slim"
enrollment_stateNoFilter courses by the caller's enrollment state
exclude_blueprint_coursesNoExclude blueprint courses from the results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changedv1.18.2
    • changedInput schema / properties / enrollment_state / description
      Previous value: -"Filter courses by the caller’s enrollment state"New value: +"Filter courses by the caller's enrollment state"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Projection mode: \"slim\" returns id/name/course_code/term/workflow_state only; \"full\" (default) returns all fields",
+  "enum": [
+    "slim",
+    "full"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / include / description
      Previous value: -"Extra fields to include on each course (Canvas include[] param)"New value: +"Extra fields to include on each course (Canvas include[] param); ignored when fields=\"slim\""
  3. First observedv1.18.0

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=true and openWorldHint=true, meaning the tool is safe and results may not be exhaustive. The description does not contradict these, but it adds limited behavioral context beyond the annotations—it doesn't mention pagination, default limits, or that results may span multiple pages, which is important for a list tool. This is a modest gap, so a 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loads the core purpose, followed by the most important usage guidance (slim vs full). It's efficient, but a couple of elements could be tightened—the list of include extras is somewhat redundant with the schema, and the final sentence about state filters is helpful but could be merged with the schema to reduce repetition. Still, no waste of words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with 5 parameters, 100% schema coverage, and read-only annotations, the description is quite complete for guiding selection and invocation. The only missing piece is explicit guidance on pagination or limits (e.g., how many results are returned per request), which is a common need. Given the tool's complexity and the richness of the schema, the description is strong overall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All five parameters are fully described in the schema with 100% coverage, so the description's job is to add context beyond that. It does explain the interaction between fields and include (ignored when slim), which is helpful, but it doesn't add much else—state and enrollment_state are self-explanatory from the schema. The baseline of 3 is fair because the schema carries most of the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('List') and resource ('courses for the authenticated user'), and clearly distinguishes this from siblings like get_my_courses or list_account_courses by scoping to the user's courses. It also introduces the fields projection modes, which are unique to this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs when to use 'slim' vs 'full' fields, telling the agent to enumerate with slim and switch to full once a target is identified. It also explains the state[] and enrollment_state filters, giving clear conditional guidance for narrowing results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools