Skip to main content
Glama
Sign In
canvas-parent-mcp

canvas-parent-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

canvas_list_recent_submissions

Read-only

Retrieve recently graded submissions for a course, defaulting to the last 14 days for the calling user. Filter by student ID or choose full or compact response details.

Instructions

List recently graded submissions in a course. Defaults to a 14-day window for the calling user.

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact removes the avatar URLs Canvas attaches to user objects (avatar_url, avatar_image_url); "full" returns Canvas's payload untouched. Link fields (url, html_url, preview_url) survive both rungs. No field projection: this server passes Canvas's payload through verbatim and has no verified record of which of its fields a caller needs.
sinceNoISO 8601 timestamp; defaults to 14 days ago.
courseIdYes
studentIdNo'self' or a numeric Canvas user ID. Defaults to 'self'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.5.4
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact removes the avatar URLs Canvas attaches to user objects (avatar_url, avatar_image_url); \"full\" returns Canvas's payload untouched. Link fields (url, html_url, preview_url) survive both rungs. No field projection: this server passes Canvas's payload through verbatim and has no verified record of which of its fields a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. Addedv1.2.5

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two useful behavioral facts — the default 14-day window and that it scopes to 'the calling user' — but says nothing about pagination, ordering, or volume, which matter for a list endpoint.

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?

Two short sentences with no filler, and the scope constraint (14-day default window) is front-loaded where an agent will see it. It is efficient, though the terseness leaves room that could have been spent on filtering guidance.

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 four parameters, one enum, no output schema, and no mutation, the description is minimally viable but thin: it omits what 'recently graded' means operationally, whether results are ordered or paged, and how the studentId filter interacts with the calling-user default.

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 a high 75% and the schema already spells out the since default (14 days ago), studentId default ('self'), and an unusually detailed view enum. The description merely restates the 14-day default already in the schema and adds nothing about view or studentId semantics, so it sits at the baseline for schema-heavy definitions.

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+resource ('List recently graded submissions') plus the scope qualifiers 'in a course' and a 14-day default window, which differentiates it from generic list tools. However, it never names the closely related siblings it could be confused with (canvas_list_missing_submissions, canvas_get_submission), so differentiation requires inference.

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?

There is no when-to-use guidance and no alternatives named. An agent cannot tell from the description when to reach for recent submissions versus canvas_list_missing_submissions or canvas_get_submission, nor what the default window implies about coverage of older work.

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