Skip to main content
Glama
Moodle MCP Server
by d1zcipline

moodle_course_structure

Retrieve a course's outline as markdown, including sections, module types, due dates, and attached files, so you can preview course contents before downloading.

Instructions

Course outline as markdown: sections, every module (assignment, file, page, url) with its type, due dates and attached files. Use it to see what the course contains before downloading anything.

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": "moodle_course_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseidYesCourse id from moodle_courses

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the output shape (markdown outline with typed modules, due dates, attachments) and implies a read-only operation, but says nothing about response size, pagination, permissions, or what happens with large courses — relevant given it enumerates every module.

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 sentences, front-loaded with the return format and contents, followed by the usage hint. No redundant phrasing and nothing that could be cut.

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?

With no output schema, the description correctly compensates by describing the returned structure in detail. The remaining gap is behavioral — no mention of size limits or truncation for large courses — but for a single-parameter read tool this is close to complete.

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?

Only one parameter, and schema description coverage is 100%, with the schema itself pointing to moodle_courses as the source of the id. The description adds no further meaning about the parameter, so the baseline 3 is appropriate.

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?

States a specific resource (course outline) and enumerates its contents — sections, modules with type, due dates, attached files — plus the output format (markdown). An agent can distinguish it from download-oriented siblings like moodle_download_file, though it does not explicitly contrast with moodle_dump_course.

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?

"Use it to see what the course contains before downloading anything" gives clear situational guidance that routes the agent toward this tool as a reconnaissance step before file retrieval. It stops short of naming an explicit alternative or stating when not to use it, so it falls short of a 5.

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