Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_peer_review_completion_analytics

Read-only

Retrieve peer review completion analytics for a Canvas assignment, including per-student breakdown and summary stats. Group by status to identify pending reviews.

Instructions

Get peer review completion analytics with student-level breakdown and summary stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assignment_idYesCanvas assignment ID
group_by_statusNoGroup students by completion status
course_identifierYesCourse code or Canvas ID
include_student_detailsNoInclude per-student breakdown

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. Changed13 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 / group_by_status / description
      Added value: +"Group students by completion status"
    • removedInput schema / properties / group_by_status / title
      Removed value: -"Group By Status"
    • addedInput schema / properties / include_student_details / description
      Added value: +"Include per-student breakdown"
    • removedInput schema / properties / include_student_details / title
      Removed value: -"Include Student Details"
    • removedInput schema / title
      Removed value: -"get_peer_review_completion_analyticsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_peer_review_completion_analyticsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_peer_review_completion_analyticsArguments"
  4. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already provide readOnlyHint: true, and the description's 'Get' is consistent. The description adds only output composition (student-level breakdown, summary stats) but no additional behavioral context such as permission requirements, default filtering behavior, or response limitations.

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 that uses every word effectively. It states the verb, resource, and key output characteristics with no redundancy or filler.

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 gives only a vague sense of the return shape ('student-level breakdown and summary stats') and does not clarify how the boolean parameters alter the output. However, the parameter schema is complete, and the tool is relatively simple, so the description is minimally viable.

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 parameters are already documented in the input schema. The description adds no extra parameter semantics or relationships beyond what the schema provides, making the baseline 3 appropriate.

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 clearly states the action ('Get') and resource ('peer review completion analytics') with an output qualifier ('student-level breakdown and summary stats'). It is specific enough to distinguish from most siblings, though it does not explicitly differentiate from the similarly named 'generate_peer_review_report'.

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?

No guidance is given about when to use this tool versus alternatives. With many peer-review sibling tools present, the description does not state exclusions or direct the agent to a better tool for other analytics needs.

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