ntulearn-mcp

Overview Schema Source Related Servers Discussions Admin

ntulearn_get_upcoming

Read-onlyIdempotent

Retrieve upcoming calendar items and assignment due dates across enrolled courses, with optional filters for course IDs, date window, item type, and pagination.

Instructions

Get upcoming calendar items and assignment due dates across your enrolled courses. Wraps Blackboard's calendar API — assignment due dates surface as items with type='GradebookColumn'. By default returns the next 2 weeks across every available course (server fans out per-course in parallel). Pass course_ids to scope to specific courses, since/until (ISO-8601) to override the window, or type to filter (e.g. type='GradebookColumn' for due dates only).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Optional calendar item type filter. Use 'GradebookColumn' for assignment due dates only.
`limit`	No	Max items to return per call (1–200, default 50). Use small values to keep results within the LLM's context.
`since`	No	ISO-8601 start of the window (e.g. '2026-05-09T00:00:00Z'). Omit to default to now.
`until`	No	ISO-8601 end of the window. Omit to default to two weeks after `since`.
`offset`	No	Number of items to skip for pagination. Use the nextOffset value returned by a previous call to walk pages.
`course_ids`	No	Optional list of course IDs to scope to. Omit to fan out across all available enrolled courses.
`response_format`	No	'json' returns a structured payload (default, recommended for agents). 'markdown' returns a human-readable summary.	json

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`hasMore`	Yes
`nextOffset`	No
`courseErrors`	No
`courseIdsQueried`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds real behavioral context, notably that the server fans out per-course in parallel and the default window/scope, which the annotations do not convey.

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?

Three sentences, each earning its place: identity first, then the type='GradebookColumn' mapping, then defaults and the three override levers. Nothing is padded and the most decision-relevant facts are front-loaded.

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?

With an output schema present and pagination documented in the schema (offset/nextOffset), the description need not explain return values. It covers scope, window defaults, filtering, and fan-out behavior; only the routing distinction from sibling due-date tools is left unstated.

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% and each parameter already documents its role, defaults, and format, so the baseline is 3. The description restates the same guidance (course_ids scoping, since/until ISO-8601 override, type filter) plus one illustrative enum value, adding modest reinforcement rather than new meaning.

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?

States a specific verb and resource ('Get upcoming calendar items and assignment due dates across your enrolled courses') and immediately clarifies the relationship to a sibling by noting that due dates surface as type='GradebookColumn' rather than as a separate resource. An agent can separate this from ntulearn_get_assignments and ntulearn_get_gradebook without opening a schema.

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?

Gives clear operating context: default window is the next 2 weeks across all courses, and it names the three levers for changing that (course_ids, since/until, type). It stops short of stating when to prefer this tool over ntulearn_get_assignments or ntulearn_get_gradebook, which are the obvious alternatives for due-date questions.

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

Deploy Server