Skip to main content
Glama
Fireiscoolsolo

Canvas LMS MCP – Local Edition

by Fireiscoolsolo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get New Quiz

get_new_quiz
Read-onlyIdempotent

Retrieve title, instructions, points, and timing for a single New Quizzes assessment; read-only and uses the Quiz LTI API, which some schools may not expose to students.

Instructions

Get details for one New Quizzes assessment: title, instructions, points and timing. Read-only. Uses the Quiz LTI API, which some schools do not expose to students. For Classic Quizzes use get_quiz.

Input Schema

NameRequiredDescriptionDefault
quiz_idYesQuiz ID (numeric string). Get it from list_quizzes, or list_new_quizzes for New Quizzes.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • changedInput schema / properties / quiz_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Quiz ID (numeric string). Get it from list_quizzes, or list_new_quizzes for New Quizzes."
  2. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description does not need to repeat safety semantics. It adds useful context beyond annotations by noting the Quiz LTI API dependency and that some schools do not expose it to students. It does not describe error behavior or response shape in detail, but the listed fields and API caveat are meaningful extra context.

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?

The description is three tight sentences with no wasted wording. It is front-loaded with what the tool does, then adds the read-only note, the API caveat, and the sibling alternative in a logical order. Every sentence earns its place.

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?

For a simple two-parameter read tool with full schema coverage, rich annotations, and no output schema, the description is complete enough. It covers purpose, return fields, API availability caveat, and sibling disambiguation. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%, and both parameters are fully documented in the input schema with clear sourcing instructions. The description does not add parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: getting details for one New Quizzes assessment. It names the fields returned (title, instructions, points, timing) and explicitly distinguishes New Quizzes from Classic Quizzes via the get_quiz sibling. An agent can select it without inspecting other tools.

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?

It clearly says when to use this tool (New Quizzes assessments) and when to use an alternative (Classic Quizzes should use get_quiz). It also warns that the underlying Quiz LTI API may not be exposed to students, which is a relevant usage constraint. This is explicit routing guidance with no ambiguity.

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