Canvas MCP Server

Overview Schema Source Related Servers Discussions Admin

Generate Peer Review Report

generate_peer_review_report

Destructive

Creates a peer review completion report with summary analytics and follow-up recommendations for a Canvas assignment, optionally saved as markdown, CSV, or JSON.

Instructions

Generate peer review completion report with summary, analytics, and follow-up recommendations.

Input Schema

Name	Required	Description	Default
`filename`	No	Custom filename for saved report
`save_to_file`	No	Save report to local file
`assignment_id`	Yes	Canvas assignment ID
`report_format`	No	Output format (markdown, csv, json)	markdown
`course_identifier`	Yes	Course code or Canvas ID
`include_action_items`	No	Include action items
`include_student_details`	No	Include student details
`include_executive_summary`	No	Include executive summary
`include_timeline_analysis`	No	Include timeline analysis

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.10.0Aug 20, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null

Changed25 schema fields changedv1.8.0Aug 10, 2026
- 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 / filename / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / filename / description
```
Added value: +"Custom filename for saved report"
```
- removedInput schema / properties / filename / title
```
Removed value: -"Filename"
```
- removedInput schema / properties / filename / type
```
Removed value: -"string"
```
- addedInput schema / properties / include_action_items / description
```
Added value: +"Include action items"
```
- removedInput schema / properties / include_action_items / title
```
Removed value: -"Include Action Items"
```
- addedInput schema / properties / include_executive_summary / description
```
Added value: +"Include executive summary"
```
- removedInput schema / properties / include_executive_summary / title
```
Removed value: -"Include Executive Summary"
```
- addedInput schema / properties / include_student_details / description
```
Added value: +"Include student details"
```
- removedInput schema / properties / include_student_details / title
```
Removed value: -"Include Student Details"
```
- addedInput schema / properties / include_timeline_analysis / description
```
Added value: +"Include timeline analysis"
```
- removedInput schema / properties / include_timeline_analysis / title
```
Removed value: -"Include Timeline Analysis"
```
- addedInput schema / properties / report_format / description
```
Added value: +"Output format (markdown, csv, json)"
```
- removedInput schema / properties / report_format / title
```
Removed value: -"Report Format"
```
- addedInput schema / properties / save_to_file / description
```
Added value: +"Save report to local file"
```
- removedInput schema / properties / save_to_file / title
```
Removed value: -"Save To File"
```
- removedInput schema / title
```
Removed value: -"generate_peer_review_reportArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"generate_peer_review_reportOutput"
```
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```
Changed1 schema field changedv1.0.0Jan 3, 2026
- addedInput schema / title
```
Added value: +"generate_peer_review_reportArguments"
```
First observedSep 27, 2025

TDQS

C2.9/5.0

Behavior2/5

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

Annotations declare destructiveHint=true and idempotentHint=false, but the description does not explain what could be destructive, whether files may be overwritten, or what side effects occur when saving reports. It adds only the report's content areas, not the behavioral context needed for a reportedly destructive operation.

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 single sentence is front-loaded and free of filler. However, for a nine-parameter report generator with file-save and destructive annotations, it is terse enough that important usage context is omitted.

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 output schema and a destructive annotation, the description should clarify side effects, file-saving behavior, and how this tool relates to the granular peer-review analytics and follow-up tools. It gives a useful high-level purpose but leaves key operational context missing.

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 schema has 100% description coverage, so all nine parameters are documented in the structured schema. The description adds no parameter-specific meaning, which is acceptable at this coverage level but does not improve on the schema.

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 states a specific verb and resource: generate a peer review completion report, and it names the included content types: summary, analytics, and follow-up recommendations. It is distinguishable from lower-level siblings such as get_peer_review_completion_analytics and get_peer_review_followup_list, though it does not explicitly say this tool aggregates them.

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 description provides no guidance on when to use this report generator rather than the many granular peer-review siblings such as get_peer_review_completion_analytics, get_peer_review_followup_list, or generate_peer_review_feedback_report. There are no exclusions, prerequisites, or recommended contexts.

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

Deploy Server

Generate Peer Review Report

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools