Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Syllabus

get_syllabus
Read-only

Retrieve full Canvas syllabus content for a course, including grading policies and exam details, with optional character limit to control output size.

Instructions

Get the complete Canvas Syllabus tab content for a course.

Unlike get_course_content_overview (which returns only a ~1000-char preview), this returns the full syllabus body so later sections such as grading policies, weighting, and final-exam details remain accessible. The syllabus is complete by default; it is cut only if you pass max_chars, and a cut is always marked with "[truncated at N characters]".

Input Schema

NameRequiredDescriptionDefault
max_charsNoOptional positive cap on the returned characters per section. When exceeded, the content is truncated with an explicit "[truncated...]" marker. Defaults to None (no truncation).
output_formatNo"text" (plain text, default), "html" (raw HTML body), or "both" (plain text followed by raw HTML)text
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. Addedv1.8.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark this as read-only, and the description adds important behavioral details: the syllabus is complete by default, truncation only occurs when max_chars is passed, and cuts are marked with '[truncated at N characters]'. This meaningfully supplements the annotation.

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 front-loaded with the core purpose, followed by a targeted comparison and a precise truncation note. Every sentence adds value without repetition or wasted wording.

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?

Given the read-only annotation, documented parameters, and lack of an output schema, the description provides sufficient context: what content is returned, how it differs from the overview sibling, and how truncation works.

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%, so the parameters are already well documented. The description reinforces the default-untruncated behavior and truncation marker for max_chars, but does not meaningfully add semantics beyond what the schema provides for output_format or course_identifier.

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: 'Get the complete Canvas Syllabus tab content for a course.' It distinguishes this tool from the preview-oriented sibling get_course_content_overview, making the purpose unambiguous.

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?

The description explicitly contrasts this tool with get_course_content_overview, explaining that this returns the full syllabus so grading policies and final-exam details remain accessible. It provides clear context for choosing this tool over the preview alternative, though it does not state explicit exclusions or when-not conditions.

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