Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Assignments

list_assignments
Read-only

List assignments in a Canvas course with filters for due date, search term, and fields, supporting slim enumeration or full details for review.

Instructions

List all assignments in a course. Use fields="slim" when enumerating assignments for selection; switch to "full" once you've identified the target. slim returns id, name, due_at, points_possible, published, and course_id only. "full" (default) includes all Canvas fields plus include extras (submission, all_dates, overrides, score_statistics, etc.). Use bucket to filter by past/upcoming/overdue/etc. Other filters: search_term, assignment_ids, order_by.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNoOnly include assignments in the given bucket
fieldsNoProjection mode: "slim" returns id/name/due_at/points_possible/published/course_id only; "full" (default) returns all fields
includeNoExtra fields to include on each assignment (Canvas include[] param); ignored when fields="slim"
order_byNoField to sort the result by
course_idYesThe Canvas course ID
post_to_sisNoFilter to assignments that are/are not posted to SIS
search_termNoPartial name substring to filter assignments by
assignment_idsNoRestrict to the given list of assignment IDs
override_assignment_datesNoApply assignment overrides to due/unlock/lock dates (default Canvas behavior: true)
needs_grading_count_by_sectionNoBreak needs_grading_count down by section

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. Changed2 schema fields changedv1.18.2
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Projection mode: \"slim\" returns id/name/due_at/points_possible/published/course_id only; \"full\" (default) returns all fields",
+  "enum": [
+    "slim",
+    "full"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / include / description
      Previous value: -"Extra fields to include on each assignment (Canvas include[] param)"New value: +"Extra fields to include on each assignment (Canvas include[] param); ignored when fields=\"slim\""
  3. First observedv1.18.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, signaling a safe read operation. The description does not contradict these. It adds context about the slim vs full return sets and mentions filters, but these details are already present in the input schema. It does not disclose additional behavioral traits like pagination, rate limits, or default ordering beyond what the schema implies. Given the annotations cover the safety profile, a 3 is appropriate – the description adds some clarity but lacks deeper behavioral context.

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 three sentences with no fluff. The primary purpose is front-loaded, followed by actionable guidance on field modes and filters. It is appropriately compact for a tool with 10 parameters. The only minor inefficiency is repeating filter names that are already in the schema, but this is acceptable for redundancy. Overall, it is well-structured and to the point.

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?

Despite having 10 parameters and no output schema, the description covers the essential usage: how to list all assignments, the two field modes, and the available filters. It does not explain pagination or default sorting, but these are not critical for an agent to invoke the tool correctly. The read-only nature is covered by annotations. The description is sufficient for an agent to understand the tool's capabilities and make initial calls, though it could include a note on result size or pagination for completeness.

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%, meaning all parameters are already documented. The description reinforces key points (e.g., 'slim' vs 'full' fields, bucket usage) but does not add new semantic meaning beyond the schema. For example, it restates that bucket filters by past/upcoming/overdue, which the schema already lists via enum and description. Since the schema does the heavy lifting, the baseline of 3 is correct; the description adds marginal value but does not compensate for any gaps (none exist).

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?

The description clearly states the tool's function: 'List all assignments in a course.' It specifies the resource (assignments), scope (course), and adds a concrete use case (enumerating for selection). While it doesn't explicitly differentiate from siblings like get_assignment or list_assignment_groups, the verb 'list' and scope are unambiguous, avoiding tautology. It could be improved by naming a sibling it is not, but the core purpose is clear.

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

Usage Guidelines4/5

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

The description provides actionable usage guidance: 'Use fields="slim" when enumerating assignments for selection; switch to "full" once you've identified the target.' This explicitly tells the agent when to use each mode. It also mentions using bucket to filter. However, it does not explicitly state when to prefer this tool over alternatives (e.g., get_assignment for a single assignment), so it lacks explicit when-not guidance. Still, the context given is valuable and specific.

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