Skip to main content
Glama
Moodle MCP Server
by d1zcipline

moodle_list_files

List every downloadable file in a course with section, module, filename, size and direct file URL, ready to pass to a download tool.

Instructions

Every downloadable file in a course: section, module, filename, size and a direct fileurl. Pass that url to moodle_download_file.

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": {
      "courseid": "<courseid>"
    },
    "name": "moodle_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 disclosure burden. It does describe the return shape (section, module, filename, size, fileurl), which is valuable given there is no output schema, but it says nothing about permissions/auth requirements, whether the listing is recursive across all modules, pagination, or possible empty results.

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, return contents front-loaded, followed by the actionable handoff. Nothing is wasted and there is no filler.

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 simple one-parameter listing tool with no output schema, the description adequately covers the returned fields and the natural next step. Minor gaps remain around pagination, scope of traversal, and authentication expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter, courseid, with 0% schema description coverage. The description implies it selects the course ('in a course') but does not clarify whether it expects a numeric course ID versus a shortname, or where to obtain that value (e.g., from moodle_courses). The schema's number type partly compensates, but the meaning added is thin.

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 states the resource concretely ('Every downloadable file in a course') and enumerates the fields returned (section, module, filename, size, fileurl), so an agent knows exactly what it gets. It implicitly distinguishes itself from moodle_download_file by naming that sibling as the next step, though it never uses an explicit verb like 'list'.

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

Usage Guidelines4/5

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

It gives clear chaining guidance: 'Pass that url to moodle_download_file', which tells the agent this is the discovery step preceding download. It does not state exclusions or prerequisites (e.g., that courseid must identify a course the user can access), but the intended usage context is unambiguous.

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