Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Diff Since Last Check

diff_since_last_check
Read-onlyIdempotent

List new Canvas grades, announcements, discussion replies, and inbox messages since a date or your last check to show what changed, remembering your last check when no date is given.

Instructions

List what changed since a given time, or since the last time you asked: newly posted grades, announcements, discussion replies and inbox messages, from your activity stream. Read-only apart from remembering when you last checked, so "what's new?" works without a date.

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": "diff_since_last_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO 8601 timestamp, e.g. 2026-09-01T00:00:00Z. Omit to use the last time this was checked (or 3 days ago the first time).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / since / description
      Previous value: -"ISO 8601 timestamp, e.g. 2026-09-01T00:00:00Z"New value: +"ISO 8601 timestamp, e.g. 2026-09-01T00:00:00Z. Omit to use the last time this was checked (or 3 days ago the first time)."
    • removedInput schema / required
      Removed value: -[
      -  "since"
      -]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description says the tool remembers when you last checked, which is a state-changing side effect. That is a direct contradiction, so this is scored 1 despite the useful disclosure of statefulness and first-run defaults.

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?

Two sentences, front-loaded with the core action and scope, with no redundant restatement of the name or title. The 'what's new?' framing earns its place by clarifying the no-date use case.

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 low-complexity, one-optional-parameter tool, the description covers scope, content categories, and no-date behavior while the schema handles timestamp details. With no output schema, it does not describe the return shape beyond listing categories, but this is a minor gap relative to the tool's simplicity.

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?

The only parameter, since, is fully documented in the schema with ISO format and default behavior. The description adds little beyond the high-level 'since a given time' meaning, so the 100% schema coverage baseline of 3 applies.

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 and resource: list what changed, scoped to newly posted grades, announcements, discussion replies, and inbox messages from the activity stream. This clearly distinguishes it from generic activity-stream and unread-count siblings.

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?

Explicitly frames usage for a given time or since the last check, including the 'what's new?' case without a date. It does not name alternatives or exclusions, such as when to prefer get_activity_stream or get_all_unread, so it falls short of a 5.

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