Skip to main content
Glama
Moodle MCP Server
by d1zcipline

moodle_course_module

Retrieves a single course module by cmid from a Moodle URL, returning its name, type, course ID, and assignment due date and description.

Instructions

One course module by cmid — the numeric id= in a Moodle URL such as /mod/assign/view.php?id=12345. Returns name, type, course id and, for assignments, the due date and description.

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": {
      "cmid": "<cmid>"
    },
    "name": "moodle_course_module"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmidYesCourse module id (id= from the URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return shape and the conditional assignment-only fields, but is silent on permissions, error behavior for invalid cmids, and whether the call is read-only (inferred from 'Returns' but not stated).

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?

One tight sentence, front-loaded with the resource and identifier, followed by the return contents. No filler and nothing that could be cut without losing 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 one-parameter read tool with no output schema and no annotations, the description covers what it fetches, how to form the id, and what comes back. Only auth/permissions and failure modes are unaddressed, which is a modest gap rather than a blocking one.

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 already 100% and the schema states cmid means 'id= from the URL', so baseline is 3. The description earns an extra point by pinning the format as numeric and showing a real URL pattern (/mod/assign/view.php?id=12345), reducing the chance of passing a slug or full URL.

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 verb+resource: fetch a single course module by cmid, and names the returned fields (name, type, course id, assignment due date/description). It implicitly contrasts with the structure/dump siblings by being single-module scoped, but never names an alternative explicitly.

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?

Gives concrete invocation guidance — cmid is the numeric id= from a Moodle URL, with an example path — but offers no when-to-use vs when-not guidance, no prerequisites, and no mention of what to do if the cmid is unknown.

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