Skip to main content
Glama
Moodle MCP Server
by d1zcipline

moodle_courses

List your enrolled courses with course IDs and names. Use the returned course IDs as the starting point for accessing assignments, deadlines, modules, and downloadable course files.

Instructions

List my enrolled courses as "id — fullname (shortname)". Start here: every other tool needs a course id or a module id taken from it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "moodle_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the return format and the identity of the ids (origin from enrollment). It does not state ordering, inclusion of hidden/archived courses, or failure behavior, which are minor but real gaps for a discovery tool.

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 short sentences, front-loaded with the action and output format, followed by the routing guidance. No filler or redundant restatement of the name.

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 zero-param, no-output-schema tool the description does the key work of describing the returned string format and its role as the entry point. Missing only secondary details such as sort order or whether all enrollment states are included.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the schema to under-document. The description adds useful context about how the ids it returns feed other tools, though that is output rather than parameter semantics.

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?

States a specific verb and resource ("List my enrolled courses") and even specifies the exact rendered output shape "id — fullname (shortname)". An agent knows precisely what comes back and can tell this apart from the course-structure and module-level siblings.

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?

"Start here: every other tool needs a course id or a module id taken from it" explicitly prescribes the sequencing and prerequisite relationship to the rest of the toolset. It leaves no ambiguity about when to call this versus the id-consuming tools.

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