Skip to main content
Glama
Sign In
ZHAW Moodle MCP Server

ZHAW Moodle MCP Server

by Dathis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

moodle_list_courses

Read-onlyIdempotent

List your ZHAW Moodle courses by status: active, past, future, or all. Choose a filter to view the relevant course list.

Instructions

List the user's ZHAW Moodle courses.

    Args:
        status: "active" (current semester, default), "past", "future" or "all"

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

NameRequiredDescriptionDefault
statusNoactive

Output Schema

NameRequiredDescriptionDefault
coursesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so no safety disclaimer is needed. The description adds the status-scoping behavior ('active' means current semester and is the default) and the available filters, which is useful but not extensive.

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?

At two short lines, the description is tight and front-loaded, with no filler or repetition of the schema. Every sentence contributes meaning.

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?

Given the single optional parameter, a default value, and an output schema, the description is nearly sufficient for correct invocation. The main omissions are an explicit note that authentication is required and a pointer to alternative list tools, but these are minor for such a simple read-only operation.

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 schema provides the status enum and default but has no descriptions, so the schema description coverage is 0%. The description compensates by clarifying that 'active' means the current semester and is the default; however, 'past', 'future', and 'all' are left to be inferred from their names.

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?

The description opens with 'List the user's ZHAW Moodle courses,' giving a concrete verb, resource, and scope. It does not explicitly distinguish itself from sibling tools like moodle_list_resources or moodle_get_course, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to choose this tool over siblings such as moodle_get_course, moodle_list_resources, or moodle_search, and no prerequisites are stated. The status parameter and its default are parameter semantics rather than usage strategy, so the tool offers no when-to-use or when-not-to-use context.

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