Skip to main content
Glama
Sign In
Canvas MCP for students

Canvas MCP for students

by AnonymousOnyx22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

What's new

get_whats_new
Read-only

Get recent Canvas announcements, newly graded assignments, and unread discussions across your courses to catch up on what changed.

Instructions

One catch up across your Canvas courses: announcements posted in the last few days, assignments graded in that window and discussions that still have unread replies. Pass since_days to change the window, 7 by default, or course_id as the Canvas course ID or as the course name to check one course. Pass limit and page to step through long lists, 20 items per section by default. Example: "What's new in Canvas since last week?"

Input Schema

NameRequiredDescriptionDefault
pageNoOptional, which page of items to show, starting at 1. Defaults to 1.
limitNoOptional, how many items to show per list. Defaults to 20.
course_idNoOptional, check one Canvas course only.
since_daysNoHow many days back to look for new announcements and newly graded work. Defaults to 7.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.9
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Optional, how many items to show per list. Defaults to 20.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Optional, which page of items to show, starting at 1. Defaults to 1.",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv0.1.5

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's job is added context, which it delivers: it discloses that results are split into three sections, that each section defaults to 20 items, and that long lists are paginated. It does not mention the 60-day cap on since_days or anything about result ordering, but the operational shape is well conveyed.

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?

Front-loaded with the aggregate purpose, then parameter behavior, then an example — a sensible order. A few phrases duplicate schema defaults (20 items, page) but they aid scanning rather than bloating the text; total length is appropriate for a four-parameter tool.

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?

With no output schema, the description must convey what comes back, and it does by naming the three result sections and their pagination. An agent can call it correctly and interpret the response. Minor gap: it doesn't say whether limit applies per section or overall, nor how empty sections appear.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description earns an extra point by clarifying that course_id accepts either a numeric Canvas course ID or a course name — information the schema does not provide. It also restates the effective defaults (7 days, 20 items) and the paging model, adding light but real meaning.

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 names a specific aggregate resource — a single catch-up across Canvas courses — and enumerates its three sections (announcements, graded assignments, unread discussions). This clearly separates it from narrower siblings like get_announcements, get_discussions, and get_todo without the agent needing to open any schema.

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?

It gives concrete invocation contexts: use it for a general catch-up, narrow with course_id to check one course, widen with since_days, and page with limit/page. It even supplies a natural-language example query. It stops short of explicit exclusions (e.g. 'for only announcements, use get_announcements'), so it is clear context rather than full routing guidance.

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