Skip to main content
Glama

What's due (Canvas)

whats_due
Read-onlyIdempotent

Lists Canvas assignments, exams, and quizzes due in the next days, grouped by class in your time zone. Filter by exams or quizzes, include submitted work, or refresh to see newly posted deadlines.

Instructions

List Canvas work due in the next days days (default 2 weeks), grouped by class, in the user's time zone. only: "" for everything, "exams" (exams, midterms, finals, tests by title) or "quizzes". Work already submitted is left out unless include_submitted is true. Canvas only knows what teachers post there: exams on Gradescope or a course site, and finals (from the registrar), won't show. refresh: true asks Canvas right now instead of using answers saved in the last few minutes (deadlines), day (class list) or week (syllabus); use it when the person says something was just posted or changed.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
onlyNo
refreshNo
include_submittedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses caching semantics (answers saved for the last few minutes, keyed by deadlines/day/week), that already-submitted work is hidden by default, and the exact blind spots of the data source (Gradescope exams, registrar finals). That is behavior an agent cannot get from the annotations or schema.

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?

The lead sentence front-loads purpose and default, then parameters follow in schema order. Dense but nearly every clause adds operative information; the `refresh` sentence is long and could be tightened slightly without losing meaning.

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

Completeness5/5

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

With an output schema present, the description need not explain return values, and it covers scope, defaults, all four parameters, exclusions, and cache behavior. Nothing an agent needs to call this correctly appears to be missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does: `days` with a 14-day default, `only` with its three literal values and the title-matching rule for exams, `refresh` with its cache-bypass meaning, and `include_submitted` with the default exclusion it overrides.

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?

The description gives a specific verb and resource ("List Canvas work due") with scope (next `days` days, grouped by class, user's time zone) and explicitly bounds the data source: Canvas only, not Gradescope or registrar finals. An agent can tell this is a due-date listing rather than a general Canvas browse or calendar query.

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 gives a concrete trigger for `refresh` ("use it when the person says something was just posted or changed") and states the default caching behavior otherwise. It does not name or contrast a sibling such as calendar_upcoming, so routing against overlapping tools is left to inference.

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