moodle-um

moodle_list_courses

List the courses a user is enrolled in and optionally filter by course name or shortname to locate relevant Moodle courses.

Instructions

List the courses the user is enrolled in.

Args: query: optional case-insensitive filter on course name or shortname.

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_list_courses"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 12, 2026

TDQS

B3.3/5.0

Behavior2/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. 'List' implies a read operation, but it says nothing about permissions, whether archived/hidden courses are included, whether results are paginated or truncated, or what a course record contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence of purpose followed by a short Args block; front-loaded and free of filler. The docstring-style 'Args:' formatting is slightly formal but not wasteful.

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

Completeness3/5

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

For a one-optional-parameter listing tool with no output schema, this covers purpose and the sole parameter adequately. It is still thin on return shape (what fields identify a course) and on result-set limits, which an agent needs before deciding to call it.

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 0% and the schema only labels the field 'Query' with type string|null. The description compensates by explaining it filters on course name or shortname and that matching is case-insensitive, which is meaningful behavior an agent could not infer from the schema.

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 and resource ('List the courses') plus a scope ('the user is enrolled in'), which lets an agent distinguish it from moodle_get_course. It does not explicitly name that sibling, so the list-vs-single distinction is inferred rather than stated.

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?

The enrollment scope implies when the tool is appropriate (the caller's own courses), but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as moodle_get_course or moodle_browser. Guidance is implied only.

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