Skip to main content
Glama

List Course Materials

list_course_materials
Read-only

Lists a course's modules and items—pages, assignments, files, and links—so you can find study material by topic and open pages for reading.

Instructions

Lists a course's modules and the items in each (pages, assignments, files, links). Use it to find the material for a topic the student wants to study, then read pages with read_course_page.

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_id": "<course_id>"
    },
    "name": "list_course_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine value beyond that by disclosing the shape of the result (modules containing items of several types), which matters because there is no output schema. It does not cover pagination or whether unpublished items are included.

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 tight sentences with zero filler; the capability statement comes first and the usage routing second. Every clause carries information.

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 single-parameter read tool with safety annotations, the definition covers purpose, return contents, and next step, which is enough to call it correctly. Minor gaps remain around volume/pagination and result ordering, but nothing blocking.

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?

There is one parameter, course_id, with 0% schema description coverage, but the name is self-explanatory and the phrase "a course's modules" implies the scoping. No additional meaning (ID source, format, or behavior on invalid IDs) is added.

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 states a specific verb and resource ("Lists a course's modules and the items in each") and enumerates the item types returned (pages, assignments, files, links). This makes it distinguishable from siblings like read_course_page or get_assignment without opening a 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?

It gives an explicit when-to-use condition ("to find the material for a topic the student wants to study") and names the follow-up tool with the condition that selects it (read pages with read_course_page). The agent is routed through a clear discovery-then-read workflow.

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