Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

upload_course_file

Upload a local file to a Canvas course. The returned file ID can be used to add the file as a module item or attach it to a conversation.

Instructions

Upload a file to Canvas course storage.

    Uploads a local file to a Canvas course. The returned file ID can be used with
    add_module_item (item_type='File') or send_conversation (attachment_ids).

    Args:
        course_identifier: Course code or Canvas ID
        file_path: Absolute path to the local file to upload
        folder_path: Canvas folder path (default: "course files" root)
        display_name: Override the filename shown in Canvas
        on_duplicate: "rename" (default) or "overwrite"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
file_pathYes
folder_pathNo
display_nameNo
on_duplicateNorename

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations, the description covers key behaviors: uploads local file, returns file ID, and explains parameters. However, it lacks details on permissions, error handling, or size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is informative but somewhat verbose, including an unformatted Args list. Could be more concise while retaining key information.

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?

The description includes return value (file ID) for downstream usage, covers all parameters, and provides integration context, making it complete for an upload tool with an output schema.

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

Parameters5/5

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

All five parameters are explained with descriptions of purpose, defaults (folder_path, display_name, on_duplicate), and example values, compensating for the 0% schema coverage.

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 clearly states the tool uploads a file to Canvas course storage and mentions integration with add_module_item and send_conversation, distinguishing its purpose.

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?

Provides clear context for when to use (uploading files) and mentions integration with other tools, but does not explicitly state when not to use or compare with sibling tools like download_course_file.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vishalsachdev/canvas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server