Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Peer Review Followup List

get_peer_review_followup_list
Read-only

Retrieves a prioritized list of students who need follow-up on incomplete peer reviews, with optional priority filtering, urgency thresholds, and contact details.

Instructions

Get prioritized list of students needing follow-up on peer review completion.

Input Schema

NameRequiredDescriptionDefault
assignment_idYesCanvas assignment ID
days_thresholdNoDays since assignment for urgency calculation
priority_filterNoFilter by priority (urgent, medium, low, all)all
course_identifierYesCourse code or Canvas ID
include_contact_infoNoInclude email addresses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed15 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / assignment_id / description
      Added value: +"Canvas assignment ID"
    • removedInput schema / properties / assignment_id / title
      Removed value: -"Assignment Id"
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / days_threshold / description
      Added value: +"Days since assignment for urgency calculation"
    • removedInput schema / properties / days_threshold / title
      Removed value: -"Days Threshold"
    • addedInput schema / properties / include_contact_info / description
      Added value: +"Include email addresses"
    • removedInput schema / properties / include_contact_info / title
      Removed value: -"Include Contact Info"
    • addedInput schema / properties / priority_filter / description
      Added value: +"Filter by priority (urgent, medium, low, all)"
    • removedInput schema / properties / priority_filter / title
      Removed value: -"Priority Filter"
    • removedInput schema / title
      Removed value: -"get_peer_review_followup_listArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_peer_review_followup_listOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_peer_review_followup_listArguments"
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes safety. The description adds that the list is prioritized and scoped to follow-up needs, but it does not explain how prioritization works, sorting behavior, or what data is included beyond the optional contact info parameter.

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?

The description is a single, front-loaded sentence with no filler. It communicates the core purpose immediately and does not waste words.

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

Completeness3/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 could do more to explain the shape of the returned list and how priority is determined. However, the full schema coverage and readOnly annotation make it minimally sufficient for invoking the tool.

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 coverage is 100%, so all five parameters are already documented in the schema. The description's mention of 'prioritized' loosely relates to days_threshold and priority_filter but adds no further semantics beyond what the schema provides.

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?

The description gives a specific verb and resource: 'Get prioritized list of students needing follow-up on peer review completion.' It is clear what the tool returns, but it does not explicitly distinguish itself from siblings like get_peer_review_completion_analytics or send_peer_review_followup_campaign.

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?

Usage is implied by 'needing follow-up,' but the description does not state when to choose this tool over alternatives such as completion analytics or follow-up campaign tools. No exclusions or prerequisites are provided.

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