Skip to main content
Glama

get_all_courses

Retrieve all available courses and their URLs from the Moodle learning platform for accessing course materials and managing academic content.

Instructions

Get all available courses and URLs from Moodle.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:108-113 (handler)
    Handler function that retrieves all courses from the MUSTerClient and formats them as a list of dictionaries containing course name and URL.
    def tool_get_all_courses() -> List[Dict[str, str]]:
        try:
            courses = muster_client.get_courses()
            return [{"name": course.name, "url": course.url} for course in courses]
        except Exception as e:
            return [{"error": f"Failed to get courses: {str(e)}"}]
  • main.py:26-30 (schema)
    Schema definition for the get_all_courses tool, specifying name, description, and no input parameters.
    Tool(
        name="get_all_courses",
        description="Get all available courses and URLs from Moodle.",
        inputSchema={"type": "object", "properties": {}, "required": []},
    ),
  • main.py:207-208 (registration)
    Registration and dispatch logic in the call_tool handler that maps the tool name to its handler function.
    if name == "get_all_courses":
        return _wrap_json(tool_get_all_courses())
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication requirements, or what format the courses/URLs are returned in. This leaves significant gaps for a tool that presumably returns data.

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 a single, efficient sentence that front-loads the core purpose with zero wasted words. Every element ('Get all available courses and URLs from Moodle') directly contributes to understanding the tool's function.

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

Completeness2/5

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

Given the tool's complexity (data retrieval with no output schema) and lack of annotations, the description is incomplete. It doesn't explain what 'all available courses' means (e.g., for current user, all in system), how URLs are structured, or the return format, leaving the agent with insufficient context for reliable use.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

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 clearly states the action ('Get') and resource ('all available courses and URLs from Moodle'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'get_course_content' or 'get_class_schedule', which prevents a score of 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?

No guidance is provided on when to use this tool versus alternatives like 'get_course_content' or 'get_class_schedule'. The description only states what it does, not when it's appropriate, leaving the agent to infer usage from context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cosmostima/MUSTer_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server