Skip to main content
Glama
Fireiscoolsolo

Canvas LMS MCP – Remote Edition

by Fireiscoolsolo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List Quiz Questions

list_quiz_questions
Read-onlyIdempotent

Retrieve a quiz's questions to review a completed, graded attempt. Read-only; questions may be hidden unless your instructor allows review, so expect permission errors or empty results.

Instructions

List a quiz's questions so you can review a completed, graded attempt. Read-only and never used to take a quiz. Canvas hides questions unless the instructor allows review, so this often returns a permission error or nothing.

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.
quiz_submission_idNoQuiz submission ID from get_my_quiz_submission.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.3
    • 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."
    • addedInput schema / properties / quiz_submission_id / description
      Added value: +"Quiz submission ID from get_my_quiz_submission."
  2. First observedv0.1.0

TDQS

A4/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, so the description is not required to restate safety. It earns credit for disclosing non-obvious behavior: Canvas may hide questions unless the instructor enabled review, so a permission error or empty result is a normal outcome rather than a failure.

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, no filler. The purpose leads, and the failure-mode caveat is packed into the trailing clause rather than a separate paragraph.

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?

Covers what the tool does, when to use it, and the common empty/error outcome — enough to call it correctly. With no output schema, a brief note on what a returned question contains would close the remaining gap.

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%, so all three parameters (course_id, quiz_id, quiz_submission_id) are already documented, including where to obtain each ID. The description adds no additional parameter meaning, which is the baseline 3 for a fully-covered schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List a quiz's questions") plus the intent ("review a completed, graded attempt"). It implicitly distinguishes itself from quiz-taking and from get_quiz, but never names the nearest sibling (get_new_quiz_items for New Quizzes) to disambiguate which endpoint returns question content.

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 clear usage context (reviewing a graded attempt) and an explicit exclusion ("never used to take a quiz"). No alternative tool is named for the New Quizzes case, so the agent must infer the split itself.

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