Canvas MCP

get-recent-updates

Retrieve recent changes and additions to your Canvas courses within a specified number of days.

Instructions

Bekijk wat er de afgelopen X dagen is aangepast of toegevoegd op Canvas

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-recent-updates"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Aantal dagen terug kijken (standaard 7)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It discloses that the tool reads recent updates over X days, but does not mention behavioral traits like auth requirements, result format, or whether it's read-only. A read operation is implied but not explicitly stated.

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?

Single sentence, front-loaded with action and resource. Efficient, though could include more detail without much overhead.

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?

For a simple tool with one parameter and no output schema, the description is minimally adequate. However, it lacks clarity on what 'updates' encompasses (e.g., assignments, grades, discussions), which could lead to misuse. Given no annotations, more context would improve 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 coverage is 100% with one parameter ('days') described as 'Aantal dagen terug kijken (standaard 7)'. The description adds the concept of 'X dagen' but does not elaborate beyond the schema. 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?

Description clearly states the verb 'bekijk' (view) and resource 'wat er is aangepast of toegevoegd op Canvas' (modified/added on Canvas). However, it does not distinguish what type of updates are included (e.g., assignments, grades, discussions) from the many sibling tools.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. The description implies usage for viewing recent changes, but lacks when-not-to-use or mention of siblings like 'get-upcoming-deadlines' or 'get-unread-announcements'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.