Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Upload Submission File

upload_submission_file
Destructive

Uploads a local file to an assignment's submission slot without submitting it, returning a file_id for later submission. Use it to stage a file before final submission.

Instructions

Upload a local file into an assignment's submission slot without submitting it. Nothing is submitted and your instructor sees nothing yet. Returns a file_id that can be submitted later through raw_canvas_request; submit_assignment_file uploads and submits in one step. [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": {
      "course_id": "<course_id>",
      "assignment_id": "<assignment_id>",
      "file_path": "<file_path>"
    },
    "name": "upload_submission_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
file_pathYesAbsolute path of the local file to upload, e.g. "C:/Users/me/essay.pdf".
assignment_idYesAssignment ID (numeric string). Get it from list_assignments or list_upcoming_assignments.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

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. Changed3 schema fields changedv1.1.3
    • changedInput schema / properties / assignment_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Assignment ID (numeric string). Get it from list_assignments or list_upcoming_assignments."
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • addedInput schema / properties / file_path / description
      Added value: +"Absolute path of the local file to upload, e.g. \"C:/Users/me/essay.pdf\"."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark this as a mutating, non-idempotent, open-world call, and the description adds genuinely new behavioral facts: it does not submit, the instructor sees nothing, and it returns a file_id for later use. The two-step preview/confirm protocol with confirm_token is disclosed in detail. The only weakness is the bracketed '[NEEDS CONFIRMATION]' qualifier, which makes it unclear whether this workflow is mandatory or merely suggested.

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 first three sentences are tight and front-loaded with the key non-submission distinction. The final bracketed paragraph is a meta-instruction with a placeholder marker and an aside about apps that can ask the user directly, which reads as internal annotation rather than tool documentation and dilutes the prose.

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 with no output schema, the description covers the essential facts: nothing is submitted yet, a file_id is returned, how to complete the submission later, and the confirmation flow. What is missing is whether the upload is reversible or whether the file attachment persists visibly in the course files area.

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 adds meaning beyond the per-field text by linking confirm and confirm_token into a required sequence ('call it again with the same arguments, confirm=true and that confirm_token'). It also clarifies what the file_id output is for, which the schema cannot convey.

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?

States a specific verb and resource ('Upload a local file into an assignment's submission slot') plus the critical scope boundary ('without submitting it'). It then names the sibling it is not, submit_assignment_file, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes to alternatives: use submit_assignment_file for upload-and-submit in one step, and raw_canvas_request to submit the returned file_id later. The confirmation sequence tells the agent exactly when to call it a second time, which is unusually concrete guidance.

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