Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Upload To My Files

upload_to_my_files
Destructive

Upload a local file into your private Canvas storage, place it in an optional folder, and get the new file ID. A preview and confirm token let you check the upload before it is carried out.

Instructions

Upload a local file into your personal Canvas storage. Only you can see it until you share or submit it. Returns the new file's ID. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

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": {
      "file_path": "<file_path>"
    },
    "name": "upload_to_my_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
file_pathYesAbsolute path of the local file to upload, e.g. "C:/Users/me/essay.pdf".
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.
parent_folder_pathNoFolder path inside your storage, e.g. "notes/spring". Omit for the top level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Set to true together with confirm_token to carry out a request you already previewed.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv1.1.3
    • addedInput schema / properties / file_path / description
      Added value: +"Absolute path of the local file to upload, e.g. \"C:/Users/me/essay.pdf\"."
    • changedInput schema / properties / parent_folder_path / description
      Previous value: -"e.g. 'my subfolder'"New value: +"Folder path inside your storage, e.g. \"notes/spring\". Omit for the top level."
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The description adds real value beyond annotations by disclosing the two-step preview/confirm protocol and the privacy model, which the annotations do not express. However, with destructiveHint=true and idempotentHint=false declared, the description never explains what is destructive — e.g. whether an existing file at the same path is overwritten — leaving an important risk unaddressed.

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?

Purpose, privacy scope, and return value come first, with the operational confirmation protocol cleanly isolated in a bracketed note. The parenthetical is dense but no sentence is filler; the mention of apps that confirm directly is a useful edge case rather than padding.

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 mutation tool with no output schema, the description covers the return value (new file ID), the visibility model, and the required confirmation sequence. The only material omission is overwrite/collision behavior, which matters given destructiveHint=true and a caller-supplied file path.

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 the baseline is 3, but the description goes further by binding confirm and confirm_token into a workflow rule ('the same arguments, confirm=true and that confirm_token'), which the schema fields only state individually. That linkage is meaningfully more than the schema provides.

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?

The description states a specific verb and resource ('Upload a local file into your personal Canvas storage') and clarifies the private-by-default scope ('Only you can see it until you share or submit it'), which implicitly separates it from upload_submission_file and upload_comment_attachment. It stops short of naming those siblings explicitly, so routing still requires the agent to infer from the sibling list.

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 bracketed note gives unusually explicit procedural guidance: call once for a preview, show it to the user, and re-call with identical arguments plus confirm=true and the token only after an affirmative answer. There is no guidance on when to pick this tool over the submission/comment upload siblings, which is the main remaining gap.

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