Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Download Submission Attachment

download_submission_attachment
Idempotent

Download one file attached to a Canvas submission and save it to local disk, returning the saved path; use a URL from list_submission_attachments.

Instructions

Download one file attached to your submission and save it to local disk. Returns the saved path. Get the URL from list_submission_attachments.

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": {
      "url": "<url>"
    },
    "name": "download_submission_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDownload URL of the attachment: the attachments[].url field from list_submission_attachments or get_my_submission. It must be an address on your Canvas.
filenameNoFile name to save as. Defaults to the attachment's own name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedInput schema / properties / url / description
      Previous value: -"Download URL of the attachment: the attachments[].url field from list_submission_attachments or get_my_submission."New value: +"Download URL of the attachment: the attachments[].url field from list_submission_attachments or get_my_submission. It must be an address on your Canvas."
  2. Changed2 schema fields changedv1.1.3
    • addedInput schema / properties / filename / description
      Added value: +"File name to save as. Defaults to the attachment's own name."
    • changedInput schema / properties / url / description
      Previous value: -"Attachment URL from get_my_submission"New value: +"Download URL of the attachment: the attachments[].url field from list_submission_attachments or get_my_submission."
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false with idempotentHint=true, and the description explains why: the tool writes a file to local disk. It also discloses the return value (saved path), which annotations cannot. It does not mention overwrite behavior if the filename already exists, which is the main remaining behavioral unknown for a disk write.

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?

Three short sentences: the action is front-loaded, the return value follows, and the sourcing hint comes last. Every sentence carries distinct information and nothing is padded.

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 two-parameter download tool with no output schema, the description covers what it does, where the required URL comes from, and what it returns. The absence of any note on local-path collisions or download failures is a minor gap given the tool's simplicity.

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%, and the schema already documents both url and filename in detail, so the baseline is 3. The description's 'get the URL from list_submission_attachments' usefully points at the source of the url value, but adds no detail on filename fallback behavior beyond what the schema states.

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?

States a specific verb and resource: download one file attached to your submission and save it to local disk, plus what it returns (the saved path). The 'attached to your submission' scope separates it from generic siblings like download_file. It stops short of explicitly contrasting with download_file or download_all_course_files, which share the same verb.

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?

Gives a concrete precondition for the required parameter: get the URL from list_submission_attachments. That is an explicit when-to-use signal rather than an implied one. It does not say when NOT to use it (e.g. for course files use download_file), so it falls just short of the top band.

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