Skip to main content
Glama

List downloadable course files

bb_list_attachments
Read-only

Lists downloadable files and posted links for a course content item, including Ultra inline files and assignment attachments, so you can identify which attachments to retrieve.

Instructions

Resolve downloadable files and posted links for a content item, including inline Ultra files and assignment attachments. Use bb_get_attachment to read file contents.

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_list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseIdYes
contentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that results span heterogeneous sources (inline Ultra files, assignment attachments), which hints at open-world variability, but says nothing about empty results, permissions, or pagination. Useful but thin beyond the annotations.

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?

Two short sentences: the capability and its scope first, the sibling hand-off second. No filler, no repetition of the title, and the relevant routing information is front-loaded.

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?

With no output schema, the description should indicate what a 'resolved' file entry contains (name, URL, id, type) so an agent knows what it can pass to bb_get_attachment. It describes the input target adequately but leaves the return shape and edge cases undefined, which is a material gap for a resolution tool.

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 description coverage is 0% and the description only implies contentId via 'for a content item'. It never explains what courseId is for, whether either ID is an opaque string, or what identifier formats are accepted, so the two required parameters remain ambiguous in both structured and unstructured fields.

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 ('Resolve') and resource ('downloadable files and posted links for a content item'), then narrows scope with 'inline Ultra files and assignment attachments'. The final sentence names the sibling that reads file contents, so an agent can separate listing from fetching 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 Guidelines4/5

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

Explicitly routes content-reading to bb_get_attachment, which clarifies that this tool is for discovery of file references only. It never states a when-not condition (e.g., for course-level or module-level files) or prerequisites, so it stops just short of full conditional guidance.

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