Skip to main content
Glama
RohanMuppa

Brightspace MCP Server

by RohanMuppa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Download File

download_file

Download a file from Brightspace course content, assignment submissions, or announcement attachments — get it inline or save it to a chosen disk path.

Instructions

Download a file from course content, assignment submissions, or an announcement's attachments. Use this when the user wants a file from Brightspace course content, dropbox submissions, or an announcement (newsId + fileId, from get_announcements). Two response modes: (1) INLINE (default — omit downloadPath): the file comes back directly in the tool response — extracted text for PDFs and Office documents, an image block for jpeg/png/gif/webp, or a short description for anything else — so it can be read immediately without touching any filesystem. This is the right choice in clients like Claude Desktop, whose analysis/sandbox tools cannot see a file the MCP server writes to its own host filesystem. (2) DISK (set downloadPath to an absolute path on the HOST filesystem the MCP server runs on): the file is saved there. Ask the user where to save it before using disk mode — never guess a directory. After identifying the file, suggest a clean readable filename (e.g., 'Lecture 7 - Memory Management.pdf' instead of 'L07_CS251_2026SP_v2.pdf') and pass it as customFilename, or omit it to keep the original. If a content-topic download fails because the file isn't released yet, the response explains why when Brightspace's module/topic metadata supports it (not yet open, ended, locked, or hidden).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileIdNoSpecific file ID within a dropbox submission, or an announcement attachment's file ID (with newsId).
newsIdNoAnnouncement (news item) ID whose attachment to download. Requires fileId.
topicIdNoContent topic ID to download (for course content files).
courseIdYesCourse ID the file belongs to.
folderIdNoDropbox folder ID (for submission/feedback file downloads).
downloadPathNoAbsolute path to the directory where the file should be saved on disk. Omit this to receive the file inline in the tool response instead — the right choice in clients like Claude Desktop, whose analysis/sandbox tools cannot see files an MCP server writes to its own host filesystem. Inline mode returns extracted text for PDFs and Office documents, an image block for jpeg/png/gif/webp, and a short description (pointing back to disk mode) for anything else, capped at 10MB and 400,000 characters of extracted text.
customFilenameNoCustom filename for the downloaded file (include extension). If not provided, uses the original filename from Brightspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.9.7
    • changedInput schema / properties / downloadPath / description
      Previous value: -"Absolute path to the directory where the file should be saved."New value: +"Absolute path to the directory where the file should be saved on disk. Omit this to receive the file inline in the tool response instead — the right choice in clients like Claude Desktop, whose analysis/sandbox tools cannot see files an MCP server writes to its own host filesystem. Inline mode returns extracted text for PDFs and Office documents, an image block for jpeg/png/gif/webp, and a short description (pointing back to disk mode) for anything else, capped at 10MB and 400,000 characters of extracted text."
    • changedInput schema / properties / fileId / description
      Previous value: -"Specific file ID within a dropbox submission."New value: +"Specific file ID within a dropbox submission, or an announcement attachment's file ID (with newsId)."
    • addedInput schema / properties / newsId
      Added value: +{
+  "description": "Announcement (news item) ID whose attachment to download. Requires fileId.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "courseId",
-  "downloadPath"
-]New value: +[
+  "courseId"
+]
  2. Changed1 schema field changedv1.0.4
    • addedInput schema / properties / customFilename / maxLength
      Added value: +255
  3. First observedv1.0.7

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it explains inline vs disk consequences, what inline returns per file type (extracted text, image block, short description), size/character caps (10MB, 400,000 chars), the requirement to ask before writing to disk, and graceful behavior when a file isn't released yet (metadata-driven explanation). This is rich disclosure of behavior beyond the structured fields.

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 and mode choice are front-loaded, and most sentences carry actionable content. It is long, and the inline-mode explanation is repeated almost verbatim in both the main description and the downloadPath schema description, which is mild redundancy but not harmful.

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?

Despite having no output schema and no annotations, the description covers the input combinations, both return modes, size limits, and failure cases in enough depth for an agent to call it correctly. Nothing essential is missing.

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 practical meaning: it pairs newsId+fileId, ties fileId to submission/announcement context, and explains the intent of customFilename (suggest a clean readable name). It goes beyond restating the schema, though the downloadPath semantics are largely duplicated from the schema's own description.

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+resource (download a file) and enumerates the three source scopes: course content, assignment/dropbox submissions, and announcement attachments. It also distinguishes the two operating modes, so an agent understands both what it does and how it returns results without opening the 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 names when to use each mode: inline is 'the right choice in clients like Claude Desktop,' disk requires asking the user for a path, and newsId+fileId come 'from get_announcements.' This gives concrete routing rules and cross-references a sibling tool rather than leaving selection to inference.

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