Skip to main content
Glama
AnonymousOnyx22

Canvas MCP for students

by AnonymousOnyx22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Upcoming due dates

get_upcoming_due_dates
Read-only

Retrieve upcoming assignments and events across all Canvas courses, sorted soonest first. Set days_ahead to limit results to a specific window, or omit it to see every due date Canvas returns.

Instructions

Upcoming assignments and events across every Canvas course, soonest first. Pass days_ahead to look only that many days ahead, for example 3. Leave it out and every upcoming due date Canvas returns is included. Example: "What is due in the next 3 days?"

Input Schema

NameRequiredDescriptionDefault
days_aheadNoOptional, how many days ahead to include. Leave it out to include every upcoming due date Canvas returns.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • addedInput schema / properties / days_ahead
      Added value: +{
+  "description": "Optional, how many days ahead to include. Leave it out to include every upcoming due date Canvas returns.",
+  "maximum": 120,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv0.1.5

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds ordering (soonest first), coverage scope (every course), and the default behavior when the optional window is omitted, which is real context beyond the annotations. It does not discuss pagination or result caps.

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?

Three short sentences, front-loaded with what the tool returns, then the parameter guidance and an example. Minor redundancy: the 'leave it out and everything is included' point duplicates the schema wording almost verbatim.

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 single-optional-parameter read-only listing tool with no output schema, the description covers scope, ordering, and default behavior well enough to call correctly. The one remaining gap is the shape of returned items (what fields accompany each due date), which an output schema would otherwise have carried.

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%, so the single parameter's meaning and omission semantics are already fully documented by the schema. The description restates this and adds only a concrete example value (3), so baseline 3 is appropriate.

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 specific verb and resource: upcoming assignments and events across every Canvas course, returned soonest first. That aggregation-across-all-courses scope helps separate it from per-course siblings like get_assignments and get_calendar_events, but those siblings are never named, so differentiation is implicit.

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?

Explains the two usage modes clearly: pass days_ahead to limit the window, omit it to get everything Canvas returns, and gives a worked example query. It stops short of saying when to prefer this over get_todo or get_calendar_events, so the alternative selection is left 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