Skip to main content
Glama
Moodle MCP Server
by d1zcipline

moodle_dump_course

Mirror a Moodle course to disk with structure, course data, all files, and assignment descriptions and attachments; save to moodle-data/, skipping already downloaded files by size.

Instructions

Mirror a whole course to disk: structure.md, course.json, every file and every assignment with its description and attachments. Saved to moodle-data/. Idempotent — already downloaded files are skipped by size.

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

Input Schema

NameRequiredDescriptionDefault
courseidYes
downloadNoDownload files too (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 burden, and it does disclose two useful traits: the fixed output location moodle-data/<courseid> and idempotency via size-based skipping. That is meaningful write-behavior context, but it omits permissions/auth requirements, what happens to files that changed but kept the same size (a real caveat of size-only skipping), error/partial-failure behavior, and overwrite semantics.

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?

Two compact sentences, front-loaded with the action and then the outputs, with no filler. Slight compression cost: the output list and the storage/idempotency facts are packed into run-on clauses, but nothing is wasted.

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?

No output schema exists, so the description must explain the result, and it does by listing the produced artifacts and destination path. However, for a multi-file disk-writing operation it says nothing about return values (counts, failures), auth, or how large courses behave, leaving gaps an agent would want before invoking.

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?

Only two parameters with 50% schema coverage: download is documented in the schema, and the description supplies meaning for courseid via "Saved to moodle-data/<courseid>" plus the file enumerate list that implies what download=true yields. That compensates for the missing courseid description better than the coverage figure alone would suggest.

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 names a specific verb and resource ("Mirror a whole course to disk") and enumerates the exact artifacts produced (structure.md, course.json, files, assignments with descriptions and attachments). It implicitly contrasts with single-file / structure-only siblings, but never names them, so sibling differentiation is left to inference.

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?

Usage is implied by the word "whole course": an agent can infer this is the bulk-mirror option versus lighter siblings like moodle_download_file or moodle_course_structure. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of cost/time for large courses.

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