Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

List Overdue Assignments

list_overdue_assignments
Read-onlyIdempotent

Find unsubmitted assignments past their due date across active Canvas courses, including items Canvas's missing flag may not catch.

Instructions

List assignments past their due date that you have not submitted, checking each active course. Read-only. Slower than list_missing_submissions, which relies on Canvas's own missing flag, but catches items without that flag.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return (one page of results). Smaller is faster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return. Smaller is faster."New value: +"Maximum number of items to return (one page of results). Smaller is faster."
  2. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only' is redundant. The description earns credit beyond them by disclosing the performance profile (slower due to per-course scanning) and the coverage caveat about items without a missing flag. It stops short of describing pagination or result shape.

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 short sentences, front-loaded with the core behavior, then the read-only guarantee, then the sibling comparison. No filler or repetition that wastes an agent's context.

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?

No output schema exists, so the description carries the burden of explaining return content, which it only implies (items, one page via limit). Still, for a one-parameter list tool with rich annotations, the important selection-critical facts—scope, cost, and why this exists alongside list_missing_submissions—are covered.

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?

The single parameter (limit) is fully documented in the schema at 100% coverage, so the baseline is 3. The description adds no syntax or constraint detail about limit, though 'checking each active course' does clarify the scan scope operated on.

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 with precise scope: assignments past due, not submitted by the caller, across each active course. It also names the sibling it differs from (list_missing_submissions), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: list_missing_submissions is faster because it trusts Canvas's missing flag, while this tool is slower but catches items lacking that flag. That is a stated cost/accuracy tradeoff an agent can act on, not just an implied usage context.

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