Skip to main content
Glama

get_quizzes

Retrieve all quizzes for a specified Canvas course by course ID, enabling AI clients to review available assessments and support course planning.

Instructions

Get all quizzes for a specific Canvas course

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>"
    },
    "name": "get_quizzes"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYesCanvas course ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and discloses almost nothing: it does not say whether unpublished/deleted quizzes are included, whether results are paginated or sorted, or what auth scope is required. "Get" implies a safe read, but that is inference, not disclosure.

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?

A single short sentence with zero filler, and the resource is front-loaded. Nothing is redundant or buried.

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 one-parameter read tool with full schema documentation and no output schema, this is close to sufficient — an agent knows what it does and what to pass. The gap is behavioral rather than structural: return shape, pagination, and quiz-state filtering are unaddressed.

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% with a single documented course_id, so the baseline is 3. The phrase "for a specific Canvas course" confirms that course_id scopes the query rather than filtering across courses, but adds no syntax, format, or edge-case detail beyond the 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 ("Get all quizzes") scoped to a specific Canvas course, which is far more than a tautology. It does not explicitly distinguish itself from siblings such as get_assignments or list_courses, but the resource noun does the disambiguating work.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives, no prerequisites (e.g., needing a valid course_id or enrollment), and no note on what it excludes. The only usage signal is the implied read of quizzes, which an agent would infer from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.