Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Course Content Overview

get_course_content_overview
Read-only

Retrieve a Canvas course overview with pages, modules, and syllabus content so you can review all course materials from one call.

Instructions

Get a comprehensive overview of course content including pages, modules, and syllabus.

Input Schema

NameRequiredDescriptionDefault
include_pagesNoInclude pages information (default: True)
include_modulesNoInclude modules and their items (default: True)
include_syllabusNoInclude syllabus content (default: True)
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed13 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / include_modules / description
      Added value: +"Include modules and their items (default: True)"
    • removedInput schema / properties / include_modules / title
      Removed value: -"Include Modules"
    • addedInput schema / properties / include_pages / description
      Added value: +"Include pages information (default: True)"
    • removedInput schema / properties / include_pages / title
      Removed value: -"Include Pages"
    • addedInput schema / properties / include_syllabus / description
      Added value: +"Include syllabus content (default: True)"
    • removedInput schema / properties / include_syllabus / title
      Removed value: -"Include Syllabus"
    • removedInput schema / title
      Removed value: -"get_course_content_overviewArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_course_content_overviewOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_course_content_overviewArguments"
  4. First observed

TDQS

B3.1/5.0
Behavior2/5

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

readOnlyHint=true already establishes the safety profile, so the description only needs to add aggregation-specific context. Instead it only restates the sections covered, which mirrors the include_* flags in the schema, and says nothing about cost, response shape, or behavior when sections are excluded.

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?

A single well-formed sentence with the verb and the three content areas front-loaded; nothing redundant or padded. It is arguably too short for the aggregation semantics, but there is no filler.

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 aggregation tool with a fully documented 4-parameter schema, the key missing piece is what the returned overview looks like and how large it can get. That gap is modest given the annotation and complete schema coverage, but it prevents a 5.

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 each of the three boolean flags is documented with its default, so the schema carries parameter meaning. The description's mention of pages/modules/syllabus loosely maps to those flags but adds no filtering or format detail beyond them.

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 a comprehensive overview of course content") and enumerates the included sections (pages, modules, syllabus). Clear on its own, but it never distinguishes itself from close siblings like get_course_structure, get_syllabus, list_pages, or list_modules, which plausibly return overlapping data.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives despite a crowded sibling set containing get_course_structure and get_syllabus. The agent must infer that this is the 'one-shot aggregate' variant versus the targeted list_* 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