Skip to main content
Glama

List Upcoming Assignments

list_upcoming_assignments
Read-onlyIdempotent

List assignments and planner items due in the next N days (default 7) across active courses, soonest first. Read-only; include completed if needed.

Instructions

List assignments and other planner items due in the next N days (default 7) across all active courses, soonest first. Read-only. Uses the same Planner feed as the Canvas dashboard; set include_completed to also show items already 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": "list_upcoming_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDefault 7
include_completedNoIf true, also include assignments you have already submitted.

Output Schema

NameRequiredDescriptionDefault
daysYes
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "days": {
      +      "type": "number"
      +    },
      +    "items": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "course_id": {
      +            "type": "string"
      +          },
      +          "due_at": {
      +            "type": "string"
      +          },
      +          "due_in": {
      +            "type": "string"
      +          },
      +          "due_local": {
      +            "type": "string"
      +          },
      +          "graded": {
      +            "type": "boolean"
      +          },
      +          "html_url": {
      +            "type": "string"
      +          },
      +          "missing": {
      +            "type": "boolean"
      +          },
      +          "plannable_id": {
      +            "type": "string"
      +          },
      +          "points": {
      +            "type": "number"
      +          },
      +          "submitted": {
      +            "type": "boolean"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "due_at"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "days",
      +    "items"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv1.0.2
    • addedInput schema / properties / include_completed / description
      Added value: +"If true, also include assignments you have already submitted."
  3. First observedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so "Read-only" in the description is redundant. The description does add two genuinely useful behavioral facts beyond the annotations: result ordering (soonest first) and the fact that results come from the same feed as the Canvas dashboard, but it leaves result caps/pagination and what "other planner items" concretely includes undisclosed.

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?

Two tight sentences with the scope and ordering front-loaded and the optional-parameter behavior trailing. Nothing is repeated for filler and every clause carries information an agent needs.

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 available, return-shape explanation is unnecessary, and rich annotations cover the safety profile. The description supplies scope, default window, ordering, and the include_completed toggle, which is nearly sufficient; only edge handling (maximum window, empty-result behavior) is unaddressed.

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%, so both parameters are already documented, and the description largely restates the default of 7. It does extend include_completed slightly beyond the schema wording ("items already done" vs "assignments you have already submitted"), which is a marginal semantic gain; baseline 3 applies.

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?

Names a specific verb and resource ("List assignments and other planner items") plus a precise scope: due in the next N days, across all active courses, soonest first. The "Planner feed" note and the time-window framing separate it cleanly from list_assignments (course-scoped), list_overdue_assignments (past due), and list_todo, so an agent can choose without opening schemas.

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?

There is implied guidance through the scope (upcoming items within a window) and one conditional hint about include_completed, but no explicit when-to-use vs when-not-to-use, and no named alternatives despite siblings like get_week_ahead, list_planner_items, and list_todo that overlap heavily.

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