Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

List Quiz Questions

list_quiz_questions
Read-onlyIdempotent

Lists quiz questions to review a completed, graded attempt; read-only, never for taking quizzes. Canvas may hide questions unless review is allowed, causing a permission error or empty result.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course_id": "<course_id>",
      "quiz_id": "<quiz_id>"
    },
    "name": "list_quiz_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
limitNoMaximum number of items to return (one page of results). Smaller is faster.
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. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum number of items to return (one page of results). Smaller is faster.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. 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."
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: Canvas visibility rules mean the call often fails with a permission error or returns nothing. That is exactly the kind of failure-mode disclosure that prevents an agent from misreading an empty result as an error.

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?

Three short sentences, front-loaded with purpose and followed by the constraint and the failure mode. "Read-only" partially duplicates readOnlyHint, a minor redundancy, but nothing else is wasted.

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 read-only list tool with five fully documented parameters and no output schema, the description covers purpose, safety, and the dominant failure mode. It does not say what a returned question looks like (e.g., whether answers or correct-answer flags are included), which is the one 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 description coverage is 100%, including page/limit semantics and where to obtain quiz_id, course_id, and quiz_submission_id, so the schema carries the parameter burden. The description only implicitly links quiz_submission_id to a graded attempt and adds no format or constraint detail beyond the schema; baseline 3 applies.

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 ("List a quiz's questions") and immediately narrows the purpose to reviewing a completed, graded attempt, which separates it from get_quiz, get_new_quiz_items, and get_my_quiz_submission. An agent can pick this tool without opening the schema.

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 when-to-use condition ("so you can review a completed, graded attempt") and an explicit when-not ("never used to take a quiz"). It does not name the sibling to use for taking a quiz or for New Quizzes items, so the routing is implied rather than spelled out.

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