Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Students Needing Attention

list_students_needing_attention
Read-only

Report students who may need instructor attention based on inactivity, missing or late submissions, and low current score.

Instructions

Report students who may need instructor attention based on inactivity, missing or late submissions, and low current score. Each finding lists the exact signals that fired and the thresholds used — this is a factual report, not a prediction. Requires instructor/TA permissions in the course.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
min_lateNoFlag students with at least N late submissions (default 3)
course_idYesThe Canvas course ID
min_missingNoFlag students with at least N missing submissions (default 1)
inactive_daysNoFlag students with no activity in the last N days (default 7)
score_thresholdNoFlag students with a current score below this value (default 70)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.15
    • addedInput schema / properties / course_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / course_id / type
      Removed value: -"number"
  2. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.18.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint true), and the description adds meaningful context beyond them: it discloses the authorization requirement (instructor/TA permissions) and the nature of the output (facts with fired signals and thresholds, not predictions). It does not cover pagination or rate limits, so not a 5.

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 tight sentences, each earning its place: the first states purpose and signals, the second clarifies report semantics, the third gives the permission prerequisite. Well front-loaded with zero filler.

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 no output schema, the description usefully explains what a finding contains (fired signals plus thresholds) and the permission requirement, which is enough for an agent to invoke it correctly. Minor gaps like output volume/pagination behavior keep it from a 5.

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 all five thresholds are documented with their defaults in the schema itself. The description mentions 'thresholds used' but adds no syntax or format detail beyond what the schema already provides, so 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?

States a specific verb (Report) and resource (students needing instructor attention) and enumerates the exact triggers (inactivity, missing/late submissions, low score). An agent can distinguish it from neighbors like list_students or get_student_analytics without opening any schema.

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?

Clearly frames the conditions under which the report is useful (students at risk on these signals) and even clarifies it is a factual report rather than a predictive one. It stops short of naming exclusion alternatives such as get_student_analytics or list_submission_comments_needing_attention, so no explicit when-not guidance.

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