Canvas MCP

get-course-files

Retrieve all files from a Canvas course, with optional filter by file type like PDF, DOCX, or PPTX.

Instructions

Haal alle bestanden van een vak op, filterbaar op type (pdf, docx, etc)

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": {
      "courseId": "<courseId>"
    },
    "name": "get-course-files"
  }
}

Input Schema

Name	Required	Description	Default
`courseId`	Yes	Het ID van het vak
`contentType`	No	Filter op bestandstype, bijv. 'pdf', 'docx', 'pptx'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations provided, so description must convey behavioral traits. It only states it retrieves files and filterable by type, but does not disclose whether it returns file metadata, contents, or any constraints like authentication or rate limits.

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?

Single sentence that is front-loaded with verb and resource. No redundant words, every part adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple parameters, description adequately states purpose and filtering, but missing details on return structure (e.g., list of file names, URLs) and pagination if applicable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds examples of valid contentType values ('pdf', 'docx', etc.), providing practical guidance beyond the schema's generic 'filter op bestandstype'.

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?

Description clearly states verb 'retrieve' and resource 'course files', and mentions filterable by type. Easily distinguishes from sibling tools like get-course-announcements or get-course-syllabus.

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

Usage Guidelines3/5

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

Description implies usage for retrieving files with optional type filter, but no explicit guidance on when to use this tool versus alternatives (e.g., get-module-content might also include files).

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