Skip to main content
Glama
NCCU-AI-SYSTEM

NCCU Moodle MCP

by NCCU-AI-SYSTEM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Open a course item

get_module

Opens a single Moodle item from its course-module id and returns its content: resources, URLs, pages, forums, assignments, quizzes, and more. Use any cmid/link to get details without needing the course id.

Instructions

Open ONE item a teacher posted and return its content, given its cmid (course-module id — the id in a /mod//view.php?id= link, or from get_course_contents). course_id is OPTIONAL — omit it and it's resolved from the cmid, so a bare cmid/link is enough. It detects the item type and returns:

  • resource/folder -> files:[{filename, mimetype, size, url}] (open the url/view_url in a browser to download; no direct download here yet)

  • url -> external_url

  • page -> html (plain text)

  • label -> text

  • forum -> forum_id + intro + discussions[] (read one with get_announcement)

  • assign -> description (instructions), attachments, due/opens/cutoff, grade_max, status, submission{submitted_at,files,text}, feedback{grade,grade_display,graded_at,comment,files}

  • quiz -> metadata + attempts · otherwise -> description

Always includes {course_id, cmid, instance, type, name, view_url}.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cmidYesCourse-module id (the id in a view.php?id= link).
course_idNoMoodle course id. Optional — resolved from cmid if omitted.

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 disclosure burden and does so thoroughly. It reveals the exact type-dependent return shapes, the always-included common fields, that file downloads must be done via browser, and that credentials come from MCP settings headers rather than from the agent. This goes well beyond a generic 'open an item' statement.

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?

The description is long due to necessary type-specific detail, but it is tightly structured with a clear opening sentence, parameter guidance, and a bullet-like breakdown of return shapes. Every sentence adds value, and the most important usage constraint is front-loaded.

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?

There is no output schema and no annotations, yet the description covers the full item-type matrix, common response fields, optional parameter resolution, download limitations, and authentication source. For an agent selecting and invoking this tool, the available context is sufficient to proceed correctly.

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 useful meaning: `cmid` is the id from `/mod/<type>/view.php?id=<cmid>` or `get_course_contents`, and `course_id` can be omitted entirely because it is resolved from `cmid`. This helps an agent construct a valid call with minimal inputs.

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: 'Open ONE item a teacher posted and return its content, given its `cmid`'. It also differentiates itself by explaining the item-type-specific behavior and explicitly routes forum reading to `get_announcement`, so an agent can distinguish it from siblings like `list_courses` or `get_course_contents`.

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?

The description gives clear context: use this tool to open a single course item from a `cmid`, optionally omitting `course_id` because it is resolved from the `cmid`. It points to `get_course_contents` as the source for `cmid` values and suggests `get_announcement` for reading individual forum posts, but it does not explicitly state exhaustive when-not-to-use conditions.

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