Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_my_upcoming_assignments

Read-only

Retrieve upcoming assignments from all Canvas courses within a specified number of days (default 7). Plan your workload by seeing pending tasks in one view.

Instructions

Get your upcoming assignments across all courses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to look ahead (default: 7)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. Changed7 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / days / description
      Added value: +"Number of days to look ahead (default: 7)"
    • removedInput schema / properties / days / title
      Removed value: -"Days"
    • removedInput schema / title
      Removed value: -"get_my_upcoming_assignmentsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_my_upcoming_assignmentsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotation readOnlyHint: true declares it as a read-only operation, and the description's use of 'Get' aligns with that. No side effects are described, which is appropriate since it is read-only. The description does not add extra transparency beyond the annotation, but it does not contradict it either.

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?

The description is one concise sentence with no unnecessary words. It is front-loaded with the core functionality and immediately clear. The parameter description is also concise and to the point.

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?

Given that there is no output schema, the description does not explain what information the returned assignments will contain (e.g., due dates, course names, status). While the purpose is clear, the agent might not know if this tool provides the specific details needed for a given task. This leaves some room for ambiguity.

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

Parameters5/5

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

The parameter 'days' is well described as 'Number of days to look ahead (default: 7)', explaining both its meaning and default value. This fully covers the semantic meaning, allowing an agent to use it correctly without ambiguity.

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 clearly states the tool's function: retrieving upcoming assignments across all courses. It uses the verb 'Get' and specifies the scope ('across all courses'), making the purpose unambiguous. It is distinct from sibling tools like 'get_my_todo_items' or 'get_course_details'.

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

Usage Guidelines3/5

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

The description does not explicitly mention when to use this tool versus alternatives. It implies it is for all courses and personal assignments, but lacks explicit guidance on when not to use it or when to prefer another tool. This is a minor gap for a simple read operation.

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