Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Score Quiz Question

score_quiz_question
DestructiveIdempotent

Score a specific question in a quiz submission. Specify attempt to score a particular attempt (omit for latest). Requires grading permissions.

Instructions

Score a specific question in a quiz submission. Specify attempt to score a particular attempt (omit for latest). Requires grading permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scoreYesThe score to assign
attemptNoQuiz attempt number to score (omit for latest)
commentNoOptional feedback comment
quiz_idYesThe Canvas quiz ID
course_idYesThe Canvas course ID
question_idYesThe Canvas quiz question ID
submission_idYesThe Canvas quiz submission ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.18.15
    • addedInput schema / properties / course_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / course_id / type
      Removed value: -"number"
    • addedInput schema / properties / question_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / question_id / type
      Removed value: -"number"
    • addedInput schema / properties / quiz_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / quiz_id / type
      Removed value: -"number"
    • addedInput schema / properties / submission_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / submission_id / type
      Removed value: -"number"
  2. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.18.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=true, which communicate safety and repeat-call behavior. The description adds genuinely useful context in stating the grading-permission requirement, but it never says that re-scoring overwrites an existing score, nor anything about partial-credit semantics — the main destructive behavior an agent should know about.

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?

Three short sentences, front-loaded with the action and free of filler; the permission note and attempt note both carry weight. It could be marginally tighter but nothing is wasted.

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?

No output schema exists, so the description would be the only place to describe what scoring returns, and it says nothing about the response. Given a 7-parameter mutation with only destructive/idempotent annotations and no return format or overwrite behavior described, the coverage is adequate but incomplete.

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 every parameter including attempt, score, and comment is already documented in the schema. The description's attempt sentence merely restates the schema's own wording ("omit for latest") and adds no syntax, range, or value semantics beyond it; 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: scoring one question within a quiz submission. An agent can tell it is a grading write, but the description never distinguishes it from the many other grading tools in the sibling list (grade_submission, submit_rubric_assessment, comment_on_submission), so sibling differentiation is left implicit.

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?

"Specify attempt to score a particular attempt (omit for latest)" gives usable guidance for one parameter and permission context ("Requires grading permissions"). However there is no when-to-use versus alternatives, e.g. this scores a single quiz question while grade_submission handles assignment submissions, so the agent must infer the routing.

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