Skip to main content
Glama
Sign In
moodle_math_mcp

moodle_math_mcp

by tab11pm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

download_course_files

Download every resource and assignment file from an entire Moodle math course by providing its course URL.

Instructions

Скачать все файлы со всего курса math Moodle целиком (resource + assign)

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": {
      "courseUrl": "<courseUrl>"
    },
    "name": "download_course_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of explaining behavior. It discloses the main action and scope (download all course files, including resource and assignment files), but it does not mention whether files are packaged, how the download is returned, or any limitations or side effects.

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?

The description is a single short sentence that leads with the core operation and scope. It is concise, though slightly redundant with 'all files' and 'entirely', and the wording is a bit awkward.

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?

There is no output schema and no annotations, so the description should explain more about what the agent can expect after invoking the tool. It provides the core scope but omits return behavior, packaging, prerequisites, and any edge-case details, leaving too much to inference.

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?

The schema has 0% description coverage and the description does not explain the courseUrl parameter at all. Although the parameter name and URI format give some clue, the description does not compensate for the missing schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Скачать' / download), names the resource ('all files from the entire course'), and specifies the included activity types ('resource + assign'). This clearly distinguishes it from sibling tools like download_module_files or list_courses.

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?

The phrase 'all files from the entire course' provides clear context for when to use this tool: when a full-course download is needed. It does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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