Skip to main content
Glama

Get Upcoming Work

get_upcoming_work
Read-only

Shows due-soon assignments, overdue unsubmitted work, and daily spaced-review counts across courses so students can plan backward from deadlines and spread study tasks.

Instructions

Shows what is due soon across courses, what is overdue and unsubmitted, and how many spaced-review items come due each day. Use it to help the student plan backwards from deadlines: spread work across the available days, start large items early, and leave time for reviews.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to look
course_idNoLimit to one course

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe read against live data. The description adds useful detail about what the view aggregates (due soon, overdue/unsubmitted, review counts per day), but says nothing about pagination, result size, or whether overdue data reflects submission status from the LMS.

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?

Two sentences, front-loaded with what is returned before the planning advice. Both sentences earn their place, though the planning sentence leans slightly toward advising the agent rather than describing the tool.

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 two-optional-parameter, read-only aggregate with no output schema, the description covers what categories of data come back and the intended workflow. Minor gaps remain around default window behavior and result volume, which are partly covered by the schema default of 14 days.

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 two optional, well-documented parameters (days, course_id), so the schema already carries parameter meaning. The description never mentions the lookahead window or course filtering, so it adds nothing on top of the schema — the baseline 3 applies.

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 uses a specific verb ('Shows') and enumerates the resource content precisely: items due soon across courses, overdue/unsubmitted work, and per-day spaced-review load. This is clearly distinguishable from single-item tools like get_assignment, though it does not explicitly contrast with the overlapping get_due_reviews or get_syllabus siblings.

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 states a clear use context — helping a student plan backwards from deadlines, spread work, start large items early, and reserve review time. That is actionable when-to-use guidance, but there are no exclusions or named alternatives for cases where a narrower tool would be better.

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