Skip to main content
Glama
Moodle MCP Server
by d1zcipline

moodle_assignment

Retrieve full assignment details—description, due and cutoff dates, max grade, attachment download URLs, and submission status—to verify deadlines and remaining submission options.

Instructions

Full assignment: description, due/cutoff dates, max grade, attachments with download URLs, and my submission status (new/draft/submitted, graded or not, can I still submit).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "moodle_assignment"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmidNoCourse module id from the URL
assignidNoAlternative: internal assignment id
courseidNoRequired together with assignid

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully discloses the shape of the return (including derived status like 'can I still submit'), but never states that this is a read-only, side-effect-free operation, nor any auth requirements or behavior when the assignment is missing or the ids are inconsistent.

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?

A single dense sentence front-loaded with the resource name and then a clear enumeration of contents. No filler; the only weakness is that the compressed noun-phrase form leaves the action verb implied.

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?

For a zero-required-parameter lookup with no output schema, the description does a good job describing what comes back, which compensates for the missing output schema. It falls short on identifier-selection guidance and on confirming read-only safety, which matter given there are no annotations to cover them.

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?

Schema coverage is 100% and each of the three parameters is documented in the schema, so the baseline of 3 applies. The description adds nothing about the parameters themselves, and notably omits the mutual-exclusivity/combination logic (cmid vs assignid vs assignid+courseid) that the schema only hints at.

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 resource (a full assignment) and enumerates its contents: description, due/cutoff dates, max grade, attachments with download URLs, and submission status. The retrieval verb is only implicit (no 'get'/'fetch'), but the scope is unambiguous and an agent can tell this is the detail view rather than the course-structure or file-listing siblings.

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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives such as moodle_course_module or moodle_download_file. Crucially, it does not say whether to prefer cmid, assignid, or the assignid+courseid pair, which is the main selection decision an agent faces here.

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