moodle-mcp

Overview Schema Source Related Servers Discussions Admin

upcoming_deadlines

Read-only

See upcoming assignment, quiz, and calendar deadlines for your courses, with status showing whether action is still needed. Filter by course and include past days to catch overdue work.

Instructions

What's due soon: assignment/quiz deadlines plus other calendar events, with whether you still need to act.

"TODO" means Moodle still expects something from you (e.g. nothing or only a draft submitted);
"done" means it doesn't (already submitted, or nothing to hand in).

Args:
    days: How many days ahead to look.
    course: Limit to one course (code like "CS-214", id, or name).
    include_past_days: Also show deadlines from the last N days (to catch overdue work).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No
`course`	No
`include_past_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations include readOnlyHint and openWorldHint, and the description adds valuable behavioral context beyond that: it defines the 'TODO'/'done' status meaning and notes that include_past_days helps catch overdue work. This clarifies the tool's output semantics without contradicting the annotations.

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 concise and well-structured: a lead sentence stating the purpose, a short clarification of the status flag, then a compact Args list. It avoids redundancy and front-loads the core functionality.

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?

The description covers all parameters, explains the output's status semantics, and mentions a useful use case (catching overdue work). With an output schema present, it does not need to detail return values. It is sufficiently complete for an agent to invoke the tool correctly.

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?

Schema description coverage is 0%, so the description is the sole source of parameter meaning. It explains 'days' as how far ahead to look, 'course' as a filter by code/ID/name, and 'include_past_days' as a way to include recent past deadlines. This fully compensates for the missing schema descriptions.

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 clearly states the tool's function: listing upcoming deadlines from assignments/quizzes and calendar events, plus a status indicator of whether action is needed. It also explains the 'TODO' vs 'done' semantics, making it distinct from siblings like 'course_overview' or 'whats_new'.

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?

The description explains how to use the arguments and what the tool does, but it does not explicitly state when to use this tool over alternatives or provide exclusion criteria. The intended use case (checking deadlines) is implied but not contrasted with sibling tools.

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

Deploy Server