Skip to main content
Glama

Next Module Items

next_module_items
Read-onlyIdempotent

Track your progress in each course's modules and list the next items to complete, including what each requires, due dates, and lock reasons. Read-only; returns IDs for marking items done.

Instructions

Show where you are in each course's modules and the next items you still have to do: what each one needs (open it, turn it in, a minimum score), when it's due, and what is locked and why. Read-only. Use it for "what's next in my classes?" Gives module_id and item_id for mark_module_item_done.

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

Input Schema

NameRequiredDescriptionDefault
course_idNoOnly this course (from list_courses). Leave it out to check your active courses, up to 10.
per_courseNoHow many next items to show for each course, 1 to 10. Default 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, open-world, and non-destructive behavior, so the description does not need to carry the full safety burden. Beyond that, it usefully describes the returned content: requirements for each item, due dates, lock status and reason, plus IDs that feed into mark_module_item_done.

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 compact and front-loads the core purpose, then adds usage context and the downstream ID handoff. The phrase "Read-only" repeats the readOnlyHint annotation, but it is brief and does not significantly reduce clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read-only tool with no output schema, the description sufficiently explains what is returned: progress, next items, requirements, due dates, lock reasons, and actionable IDs. Together with the annotations and complete schema descriptions, an agent has enough information to call and use the tool correctly.

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 description coverage is 100%, with both parameters fully documented, including course filtering and per-course item count defaults and limits. The description does not add parameter-specific meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 and resource: it shows module progress and the next outstanding items, including requirements, due dates, and lock reasons. It clearly distinguishes this from merely listing all module items by focusing on what remains to be done and by returning module_id/item_id for mark_module_item_done.

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?

It gives a clear usage cue with the quoted question "what's next in my classes?" and points to mark_module_item_done as the follow-up action using the returned IDs. It does not explicitly name when not to use it or contrast it with list_module_items, but the intended context is clear.

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