Skip to main content
Glama

get_upcoming_assignments

Retrieve upcoming assignments from all Canvas courses with future due dates to plan coursework and track approaching deadlines.

Instructions

Get upcoming assignments across all courses with future due dates

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_assignments"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, and it leaves key traits unstated: how far ahead 'upcoming' reaches, whether results are sorted by due date, whether already-submitted items are included, and how assignments without a due date are handled. It does imply a read-only, cross-course listing, but that is the minimum.

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 nine-word sentence that front-loads the action and resource and adds the scope constraint without padding. Nothing could be removed without losing information.

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

Completeness2/5

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

With no input schema fields, no annotations, and no output schema, the description is the only source of information about results, yet it never says what an 'assignment' record contains, what order results arrive in, or what 'upcoming' window is applied. For a zero-parameter listing tool this leaves the agent guessing at the shape of the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to convey; the baseline of 4 applies. Nothing in the description misleads about inputs.

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 and resource ('Get upcoming assignments') plus a scope qualifier ('across all courses with future due dates'), which is more precise than the sibling get_assignments. It stops short of naming any sibling to contrast with, so the boundary is only implied by the word 'upcoming'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'future due dates' hints at when this is appropriate, but there is no explicit guidance about when to pick this over get_assignments or get_todo_items, which sit in the same space. The agent must infer the distinction from a single adjective.

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