Skip to main content
Glama
Sign In
enauczanie-mcp

enauczanie-mcp

by Zambrzyckii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_deadlines

Lists assignment due dates and quiz closing times across all your Moodle courses within a chosen time window, sorted soonest first, so you can plan upcoming work.

Instructions

List assignment due dates and quiz closing times across all courses, from days_back days ago to days_ahead days ahead, soonest first.

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

Input Schema

NameRequiredDescriptionDefault
days_backNo
days_aheadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. 'List ... soonest first' correctly conveys a read-only operation and discloses result ordering and cross-course aggregation, but it says nothing about result volume, pagination/truncation, or whether already-submitted assignments are included.

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 well-formed sentence with the resource, scope, time window, and ordering each appearing once. Nothing is redundant and the most important information (what is listed, over what range) leads.

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?

For a read-only, two-optional-parameter listing tool with no output schema, the definition covers scope, window, and ordering adequately. The remaining gaps (default values and per-deadline return fields) are minor but would have been cheap to add.

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 0%, so the description must compensate. It defines the two parameters as offsets in days backward and forward, which is more than the schema gives, but it omits the defaults (1 and 14), does not say whether days_back>0 re-includes past due dates, and does not clarify unit edge cases like 0.

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 ('List') and a precise composite resource: assignment due dates plus quiz closing times, explicitly scoped 'across all courses.' That scope plus the soonest-first ordering separates it from list_assignments and get_quiz_review, though no sibling is named explicitly.

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 days_back/days_ahead window implies when the tool is applicable (upcoming or recent deadlines), but there is no explicit when-to-use guidance, no exclusion of alternatives such as list_assignments, and no note about what happens to deadlines outside the window.

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