Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Find Exams

find_exams
Read-onlyIdempotent

Identify upcoming exams, midterms, finals, and tests across courses, with dates, points, grade impact, and selection reasons; read-only, so confirm details in the syllabus.

Instructions

Find upcoming exams, midterms, finals and tests across your courses: the date, points, about how much of your grade each one is, and why it was picked (its name, its assignment group or a course calendar event). Read-only. It is a best guess, so tell the student to check the syllabus. Use it for "when are my exams?"

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to look, 1 to 180. Default 60.
course_idNoOnly this course (from list_courses). Leave it out to check your active courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the description's added value is the reliability warning: results are a best guess and the student should be told to check the syllabus. That is genuinely useful, non-annotated context. It does not discuss rate limits or result limits, which keeps it off a 5.

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 you get, then the read-only and reliability caveats, then the usage trigger. It is somewhat conversational and the quoted example sentence is borderline filler, but each sentence carries a distinct point.

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 two-parameter read tool with no output schema, the description covers return fields, reliability, and usage intent, which is nearly everything an agent needs. Only minor gaps remain around the default look-ahead window and course scoping.

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% and both parameters carry their own descriptions, so the schema does the heavy lifting. The description adds only implicit scope ('across your courses', matching the default of active courses) and never explains the days window.

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 (find exams) and enumerates the exact return fields: date, points, grade weight, and the reason each was picked (name, assignment group, or calendar event). An agent can tell this is an exam-discovery tool, not a general assignment or deadline lookup.

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 a concrete triggering question ('when are my exams?') and frames the scope as across your courses. It does not name alternatives or say when not to use it, so it falls short of explicit exclusions, but the intended context is clear.

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