Skip to main content
Glama

Browse course files and links

bb_get_course_content
Read-only

Retrieves a flattened course outline with modification dates, attachment metadata, and posted links to help locate newly uploaded lectures for reading.

Instructions

Flatten the course outline with modification dates, attachment metadata and posted links. Use this to find the latest uploaded lecture, then bb_get_attachment to read it.

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>"
    },
    "name": "bb_get_course_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered structurally. The description adds that results are flattened and enriched with dates and attachment metadata, which is real behavioral context. It says nothing about pagination behavior despite limit/offset parameters, nor about result volume or ordering.

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?

Two tight sentences: the output shape comes first, the actionable next step second. Nothing is redundant. It is short enough that the missing parameter and pagination detail reads as an omission rather than padding.

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

Completeness2/5

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

With no output schema, zero schema coverage on three parameters and no pagination guidance, the definition leaves an agent unable to call it precisely — paging through a flattened outline is the obvious real use case and is unaddressed. The workflow handoff to bb_get_attachment is the one complete piece.

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%, so the description carries the full burden for three parameters. It never explains courseId, and limit/offset are completely unaddressed — no default, no maximum, no paging semantics. The reader learns only what the payload contains, not how to control it.

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?

"Flatten the course outline with modification dates, attachment metadata and posted links" gives a specific verb plus a clear picture of the returned resource, including what fields are enriched. It does not distinguish itself from near-name siblings like bb_get_content, bb_list_content or bb_browse_course, so an agent cannot fully disambiguate without opening other schemas.

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?

The description supplies a concrete workflow: use this to locate the latest uploaded lecture, then pass to bb_get_attachment. That is genuinely useful routing. However it gives no when-not guidance against the several look-alike content listing tools, which is the harder selection problem here.

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