Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Get Change Log

get_change_log
Read-onlyIdempotent

Lists what this server changed in Canvas, newest first—when, tool, course/item IDs, status, and confirmation—so you can audit changes. Read-only and makes no Canvas calls.

Instructions

List what this server changed in Canvas, newest first: when, which tool, the course and item IDs, whether it went through (done, failed, cancelled or refused) and how it was confirmed. Read-only, makes no Canvas calls and works before a token is set. Use it for "what did you change in my Canvas?" It keeps IDs only, never message text. CANVAS_CHANGE_LOG=off turns recording off.

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_change_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many changes to show, newest first, 1 to 200. Default 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare the safe read-only profile, yet the description adds materially new behavior: newest-first ordering, the exact status vocabulary (done, failed, cancelled, refused), confirmation tracking, the fact that it makes no Canvas API calls, that it works pre-auth, that it stores IDs only and never message text, and the CANVAS_CHANGE_LOG=off kill switch. None of that is recoverable from the annotations.

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-loads what it does and the ordering before preconditions and privacy notes; every clause carries information. The status enumeration and the env-var sentence are slightly dense but both earn their place. Minor overlap between "Read-only" and "makes no Canvas calls," the latter being the informative part.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries responsibility for return shape — and it does, listing timestamp, tool, course/item IDs, outcome status, and confirmation. Ordering, preconditions, privacy limits, and the disable switch are all covered, so an agent could call this correctly without any other information.

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% and the single `limit` parameter already documents range and default, so the description's job here is minimal. It reinforces the "newest first" ordering, which aligns with the schema, but adds no syntax or edge-case detail beyond it — baseline 3.

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?

Names a specific verb and resource ("List what this server changed in Canvas") plus the ordering ("newest first") and the exact fields returned (when, which tool, course/item IDs, outcome, confirmation). The qualifier "this server changed" and "makes no Canvas calls" distinguishes it from the many Canvas activity-stream siblings an agent could confuse it with.

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?

Gives an explicit use case ("Use it for 'what did you change in my Canvas?'") and preconditions ("works before a token is set"), which tells the agent when this is the right call. It does not name a contrasting alternative or state when not to use it, 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