Skip to main content
Glama
Sign In
moodle-watch

moodle-watch

by Valej18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

deadlines

List upcoming due items soonest first, flagging any that have moved from their original date and showing the previous due date.

Instructions

Upcoming deadlines, soonest first.

moved is true when the due date changed since it was first seen, and moved_from gives the previous one. No Moodle API reports this; it is known only because the ledger saw the earlier value.

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": "deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
withinNo30d
include_pastNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It adds context about the 'moved' field and its origin (ledger observation), which is useful, but it does not state whether the operation is read-only, has side effects, or any other behavioral traits. Partial transparency.

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?

The description is two sentences, with the main purpose front-loaded in the first sentence. It is concise without waste, and the additional note about 'moved' is clearly separated.

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?

While an output schema exists (so return values need not be explained), the description omits any explanation of the input parameters, which are non-trivial with defaults. This leaves a significant gap for correct invocation, making the description incomplete for a tool with these context signals.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention either parameter ('within' or 'include_past'). An agent receives no explanation of what these parameters mean or how to use them, so the description fails to compensate for the schema gap.

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 states the tool lists upcoming deadlines sorted soonest first, which is a clear verb and resource. It does not explicitly differentiate from siblings like backlog or whats_new, but the purpose is specific enough that an agent can infer its use.

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 is provided on when to use this tool versus alternatives. The description does not mention scenarios, exclusions, or prerequisites, leaving the agent to guess whether this is the right choice for a given request.

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