Skip to main content
Glama
Sign In
edhec-mcp

edhec-mcp

by Sillvs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Download course files

bb_download_files
Idempotent

Save Blackboard course file attachments to a local folder while preserving folder structure; existing files are skipped and external links are listed instead of downloaded.

Instructions

Save all file attachments of a course (or one folder) into a local folder, keeping the structure. Existing files are skipped. External links (e.g. Harvard course packs) are listed, not downloaded.

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": "<course>",
      "destDir": "<destDir>"
    },
    "name": "bb_download_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYesCourse: internal id like "_12345_1", a course URL, or the course code
destDirYesAbsolute local folder to save into
folderIdNo
skipExistingNoDefault true. If false, existing files are kept and new copies saved as "name (1).ext". Nothing is ever overwritten.
onlyContentIdsNoOnly these content item ids
includeExecutablesNoAlso save programs/scripts (.app, .pkg, .sh, .exe ...). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses that directory structure is preserved, existing files are skipped, and external links are only listed rather than fetched — useful context for a tool that writes to the local filesystem. It does not say what the tool returns (e.g. where the external-link list appears or what summary is produced), which matters since there is no output schema.

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, each earning its place: capability and scope first, then the overwrite policy, then the external-link caveat. No filler or redundancy.

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 six-parameter download tool with no output schema, the description covers the essential behaviors (scope, structure preservation, skipping, link handling). The main gap is the return value — an agent cannot tell whether the external-link list and download counts come back in the response or elsewhere.

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 coverage is 83%, so the schema already documents course, destDir, skipExisting, and includeExecutables thoroughly. The description only implies the folder scope (folderId) and echoes the skip-existing behavior; it says nothing about onlyContentIds or executable inclusion, so it adds little beyond the schema.

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 gives a specific verb and resource — saving all file attachments of a course (or one folder) into a local folder — and clearly separates this from listing-oriented siblings such as bb_course_contents by stating that files are actually written to disk.

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?

It states the two scopes (whole course or a single folder) and what happens to already-existing files and external links, giving clear context for use. It never names an alternative tool or an explicit when-not-to-use condition, so it stops short of full routing 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