Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Assignments

list_assignments
Read-only

Retrieves all assignments for a specific Canvas course using its course code or Canvas ID. Use it to review assignment details and due dates for a course.

Instructions

List assignments for a specific course.

Input Schema

NameRequiredDescriptionDefault
raw_datesNoAppend a JSON block with each assignment's due_at, unlock_at, lock_at, updated_at, all_dates and checkpoint dates exactly as Canvas returns them (null stays null). Use it for due-date audits: a checkpointed discussion has a null due_at and its dates on the checkpoints. Default False.
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • addedInput schema / properties / raw_dates
      Added value: +{
+  "default": false,
+  "description": "Append a JSON block with each assignment's due_at,\nunlock_at, lock_at, updated_at, all_dates and checkpoint dates\nexactly as Canvas returns them (null stays null). Use it for\ndue-date audits: a checkpointed discussion has a null due_at\nand its dates on the checkpoints. Default False.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  3. Changed7 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • removedInput schema / title
      Removed value: -"list_assignmentsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"list_assignmentsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"list_assignmentsArguments"
  5. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing beyond that — no note on whether unpublished/inactive assignments appear, whether results are paginated, or how the raw_dates flag changes behavior (that detail lives only in the schema).

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?

A single short sentence with the scope front-loaded and zero filler. It is efficient, though the brevity borders on under-specification rather than optimal conciseness.

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

Completeness3/5

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

The tool is simple (2 params, one required) and annotations cover safety, but with no output schema the description omits any hint of the return shape — whether it lists all assignments or only those visible to the caller, and whether results are truncated or paginated. Adequate but with a real gap for a listing tool.

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?

Schema description coverage is 100%, including a detailed explanation of raw_dates and course_identifier, so the schema carries parameter meaning. The description only implies the course_identifier requirement via 'for a specific course' and contributes no additional semantic detail, matching the baseline of 3.

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

Purpose4/5

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

States a clear verb+resource (list assignments) and a scope (for a specific course), so an agent knows what it retrieves. However, it does nothing to distinguish it from siblings like get_assignment_details, list_submissions, or get_my_upcoming_assignments, which all touch the same domain.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives such as get_assignment_details (single assignment) or get_my_upcoming_assignments (personal upcoming). No prerequisites, no exclusions, no implied context beyond the one-line purpose.

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