Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

List Assignments

list_assignments
Read-onlyIdempotent

Lists a course's assignments with due dates, points, and submission status; filter by bucket or name to find upcoming, overdue, or specific work.

Instructions

List assignments in a course with due dates, points and your submission status, optionally filtered by bucket (e.g. upcoming, overdue) or name. Read-only. Use get_assignment for one assignment's full instructions and rubric.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course_id": "<course_id>"
    },
    "name": "list_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
limitNoMaximum number of items to return (one page of results). Smaller is faster.
bucketNoOptional filter: "past", "overdue", "undated", "ungraded", "unsubmitted", "upcoming" or "future".
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
search_termNoOptional text filter on names or titles (at least 2 characters, case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return. Smaller is faster."New value: +"Maximum number of items to return (one page of results). Smaller is faster."
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed4 schema fields changedv1.1.3
    • addedInput schema / properties / bucket / description
      Added value: +"Optional filter: \"past\", \"overdue\", \"undated\", \"ungraded\", \"unsubmitted\", \"upcoming\" or \"future\"."
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
    • addedInput schema / properties / search_term / description
      Added value: +"Optional text filter on names or titles (at least 2 characters, case-insensitive)."
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the 'Read-only' sentence adds nothing. What the description does add beyond structured data is the shape of the payload — items include due dates, points, and the caller's own submission status — which matters because there is no output schema. It does not discuss empty-result or not-enrolled behavior, but that is a minor omission.

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

Conciseness5/5

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

Three short sentences with the capability, filters, and the alternative sibling in that order. No filler and nothing repeated between sentences.

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

Completeness5/5

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

For a read-only list tool with one required parameter and a fully documented schema, the description covers what is returned, how to narrow results, and which sibling to use instead. Pagination is handled in the schema's own page/limit descriptions, so nothing essential is missing.

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 coverage is 100%, with every parameter, including the bucket enum and search_term's 2-character minimum, already documented in the schema. The description only restates the bucket values with examples ('upcoming, overdue') and mentions name filtering, which is a marginal addition. Baseline 3 applies when the schema carries the semantics.

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?

States a specific verb (list) and resource (assignments in a course) and enumerates what each item carries: due dates, points, and the caller's submission status. It also explicitly distinguishes itself from the single-item sibling by naming get_assignment and what that tool adds (full instructions and rubric).

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?

Gives a clear when-not: use get_assignment instead when you need one assignment's instructions and rubric. It also implies the filtering use case via the bucket examples (upcoming, overdue) and the name filter. It stops short of routing to the near-duplicate siblings list_upcoming_assignments and list_overdue_assignments, leaving that choice to inference.

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