Skip to main content
Glama
Sign In
moodle-mcp

moodle-mcp

by ralstonraphael
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

moodle_download

Download a Moodle file to a local folder, defaulting to ~/Downloads/Moodle, and return its saved path.

Instructions

Save a Moodle file to disk (default ~/Downloads/Moodle) and return the local path.

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": {
      "fileurl": "<fileurl>"
    },
    "name": "moodle_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileurlYes
dest_dirNo~/Downloads/Moodle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write-to-disk, non-destructive, network-bound profile is covered. The description adds the default target directory and the returned local path, but says nothing about overwrite behavior, permissions, or failure modes.

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?

A single front-loaded sentence with zero filler that names the action, the default location, and the return value. Nothing to trim.

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?

With no output schema, the description usefully states that the local path is returned, and annotations cover the safety profile. However, for a 2-param tool with 0% schema coverage it omits how to obtain fileurl and what happens on existing files or errors.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and largely does not. It implies fileurl is a Moodle file URL and repeats the dest_dir default already present in the schema, but gives no format, provenance, or validation detail for the required fileurl.

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+resource ('Save a Moodle file to disk') plus the default destination and the return value (local path). This clearly differentiates it from read-oriented siblings like moodle_read and moodle_file_text, though it does not name them explicitly.

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 on when to download versus reading a file with moodle_read or moodle_file_text, and no note on where the required fileurl comes from (e.g., moodle_course_contents). Usage is only implied by the verb 'Save'.

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