Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create New Quiz

create_new_quiz
Destructive

Creates a New Quiz (LTI) in a Canvas course, with configurable title, due dates, publishing, and instructions.

Instructions

Create a New Quiz (LTI) in a Canvas course. New Quizzes is the modern quiz engine; for Classic quizzes use create_quiz.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the quiz
due_atNoISO-8601 due date
lock_atNoISO-8601 lock time
course_idYesThe Canvas course ID
publishedNoWhether the quiz is visible to students
unlock_atNoISO-8601 unlock time
instructionsNoHTML instructions shown before the quiz starts
points_possibleNoTotal points; defaults to sum of item points

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv1.18.8
    • removedInput schema / properties / instructions / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / instructions / type
      Added value: +[
+  "string",
+  "null"
+]
  3. First observedv1.18.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already signal a write operation via destructiveHint, and the description accurately describes a create action. It adds the LTI detail and the New vs. Classic quiz distinction, but does not elaborate on side effects, permissions, or draft/published behavior beyond the schema.

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 short, front-loaded sentences state the core operation and the key distinction from the alternative tool. There is no unnecessary detail or repetition of schema information.

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 create operation with 100% schema coverage and no output schema, the description provides the essential context: it creates a New Quiz, uses LTI, and tells the agent which sibling tool to use for Classic quizzes. It could add default behavior (e.g., draft vs. published), but the absence is not critical given the schema covers the published parameter.

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 schema already documents all parameters with descriptions, so the tool description does not need to restate them. However, the description also does not add any extra parameter-level guidance beyond what the schema provides.

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 action ('Create'), a specific resource ('New Quiz'), and the target environment ('Canvas course'). It also distinguishes this from the Classic quiz tool, leaving no ambiguity about what this function does.

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

Usage Guidelines5/5

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

The description explicitly tells the agent to use create_quiz for Classic quizzes and identifies New Quizzes as the modern engine. This is clear alternative-selection guidance for an agent choosing between sibling tools.

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