Skip to main content
Glama

Read course attachment contents

bb_get_attachment
Read-only

Download and extract text from Blackboard course attachments such as PDF, PPTX, DOCX, XLSX, notebooks, HTML, and text, returning savedPath and pagination for long files.

Instructions

Download and read PDF, PPTX (slide text and speaker notes), DOCX, XLSX (CSV per sheet), Jupyter notebooks, HTML and text. Returns extracted text plus savedPath and limitations. Continue long files with nextOffset. No code execution or OCR. Does not submit or modify Blackboard.

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": {
      "courseId": "<courseId>",
      "contentId": "<contentId>"
    },
    "name": "bb_get_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdNoFile ID or filename from bb_list_attachments; required for multiple files
offsetNo
courseIdYes
pageSizeNo
contentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the readOnly/openWorld annotations: explicit exclusions (no code execution, no OCR, does not submit or modify Blackboard) and a description of what is returned (extracted text, savedPath, limitations). What is missing are operational details such as size limits or failure behavior on unsupported formats.

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 dense sentences, format list front-loaded, exclusions and continuation behavior packed into short clauses with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The return description (text plus savedPath and limitations) compensates for the absent output schema and the readOnly annotations cover safety, but with 5 parameters at 20% schema coverage the description leaves most inputs undefined, which is a real gap for an agent assembling a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 20%, so the description carries the burden, yet it explains only the continuation parameter and calls it 'nextOffset' while the schema names it 'offset'. fileId, courseId, contentId and pageSize receive no meaning from the description at all.

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 ('Download and read') and enumerates the exact formats handled (PDF, PPTX with speaker notes, DOCX, XLSX as CSV per sheet, notebooks, HTML, text), which no sibling tool claims. An agent can distinguish it from bb_get_content or bb_read_link on the basis of attachment handling alone.

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

Usage Guidelines3/5

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

Provides implicit guidance in the form of continuation instructions ('Continue long files with nextOffset') and constraints ('No code execution or OCR'), but never says when to choose this over bb_read_link or bb_get_content, nor when an attachment should be skipped.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.