Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get My Peer Reviews Todo

get_my_peer_reviews_todo
Read-only

Retrieve Canvas peer reviews you still need to complete, optionally filtered by course or assignment, so you can identify outstanding review tasks.

Instructions

Get peer reviews YOU need to complete.

Input Schema

NameRequiredDescriptionDefault
course_identifierNoCourse code or Canvas ID (omit for all courses). Required if assignment_identifier is given.
assignment_identifierNoCanvas assignment ID to check directly, bypassing the per-course discovery scan. Use this when you already know which assignment has your peer review — the discovery scan only queries assignments whose "peer_reviews" flag came back true on the course's assignment listing, so an assignment where that flag is missing or stale for any reason would otherwise be silently skipped.

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. Changed2 schema fields changedv1.9.0
    • addedInput schema / properties / assignment_identifier
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Canvas assignment ID to check directly, bypassing\nthe per-course discovery scan. Use this when you already know which\nassignment has your peer review — the discovery scan only queries\nassignments whose \"peer_reviews\" flag came back true on the course's\nassignment listing, so an assignment where that flag is missing or\nstale for any reason would otherwise be silently skipped."
+}
    • changedInput schema / properties / course_identifier / description
      Previous value: -"Course code or Canvas ID (omit for all courses)"New value: +"Course code or Canvas ID (omit for all courses).\nRequired if assignment_identifier is given."
  3. Changed7 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID (omit for all courses)"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • removedInput schema / title
      Removed value: -"get_my_peer_reviews_todoArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_my_peer_reviews_todoOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Addedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description contributes the scoping semantics (current user, incomplete items only), but says nothing about return shape, whether completed reviews are excluded, or what happens when no course/assignment filter is supplied.

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?

A single short sentence with the key qualifier ('YOU') front-loaded and no wasted words. It is efficient but arguably under-informative for the ambiguity against sibling peer-review tools.

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 and only a readOnly annotation, the schema does the heavy lifting on parameters, but the description leaves open what the results contain and how this differs from the several adjacent peer-review listing tools. Adequate for a simple read, but not complete enough to disambiguate confidently.

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% and both parameters carry detailed descriptions, including the note that assignment_identifier bypasses the per-course discovery scan. The description adds nothing beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource plus a scope qualifier ('peer reviews YOU need to complete'), which conveys that it returns the caller's outstanding peer-review obligations rather than all peer reviews. It does not, however, distinguish itself from siblings like list_peer_reviews, get_peer_review_assignments, or get_peer_review_followup_list, all of which plausibly overlap.

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 only implied by the phrase 'YOU need to complete' — an agent can infer this is the personal outstanding-work list. There is no explicit when-to-use guidance, no mention of when to prefer list_peer_reviews or the followup-list sibling, and no stated prerequisites.

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