Skip to main content
Glama
NCCU-AI-SYSTEM

NCCU Moodle MCP

by NCCU-AI-SYSTEM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get course contents

get_course_contents

Retrieve all teacher-posted materials for a Moodle course, grouped by weekly sections. Shows resources, links, forums, assignments, and summaries, with optional blank sections.

Instructions

Get everything the teacher posted in one course (by Moodle course id, from list_courses), grouped by section — NCCU names sections by week, so this is the week-by-week list of materials, links, forums and assignments.

The summary is the teacher's text for that section/week (readings, plan, notes) — many NCCU weeks have only a summary and no attached items. By default a section is shown if it has items OR a summary; only truly blank sections are dropped. Set include_empty true for the full week skeleton including blank weeks.

Each section: {section_id, section, summary, modules:[{id, instance, name, type, url}]}. type is the Moodle module (assign, resource, url, forum, quiz, page, folder, label, …); id is the course-module id (cmid) and instance the activity id — use them to open an item with other tools (e.g. an assign instance is the course_id-independent assignment id, a forum instance feeds get_announcement's forum).

Credentials come from the MCP settings headers, not from you.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesMoodle course id (from list_courses).
include_emptyNoInclude truly blank sections (no items and no summary).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it is highly transparent: it explains default section filtering, the effect of include_empty, the meaning of module fields, and that credentials come from MCP headers rather than the caller. It does not claim a read-only flag, but 'Get' plus the absence of any mutation language aligns with a retrieval operation.

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?

Although long, every sentence earns its place: purpose, filtering behavior, output structure, cross-tool routing, and authentication. The main purpose is front-loaded, and the later paragraphs provide necessary detail for a tool with no output schema.

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

Completeness5/5

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

The description completely compensates for the missing output schema by specifying the section and module object shapes, default behavior, and how ids connect to other tools. There are no obvious gaps in what the agent needs to call or interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful context: course_id is tied to list_courses, and include_empty is explained as showing the 'full week skeleton including blank weeks.' This enriches the schema's terse descriptions without being redundant.

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 opens with a specific verb and resource: 'Get everything the teacher posted in one course', and adds that results are grouped by section/week. It distinguishes itself from sibling tools by asserting a comprehensive week-by-week list of materials, links, forums and assignments, unlike narrower tools like list_assignments or get_announcement.

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?

It clearly states the input comes from a Moodle course id obtained from list_courses, and it shows how the output ties to other tools (e.g., a forum instance feeds get_announcement). However, it never explicitly states when not to use this tool or names alternative tools for narrower cases.

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

Deploy Server

Other Tools