Skip to main content
Glama
Sign In
Canvas LMS MCP Server

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Rubric

get_rubric
Read-only

Retrieve a single Canvas rubric definition by course and rubric ID, including criteria, rating levels, points, and optional assignment association IDs for assessment workflows.

Instructions

Get a single rubric's definition (title, points_possible, criteria, and rating levels) by ID. Use list_rubrics to find the rubric_id for a course first. Pass include=["assignment_associations"] to also retrieve the rubric association IDs that submit_rubric_assessment needs, or include=["assessments"|"graded_assessments"|"peer_assessments"] for assessor_id-only assessment summaries (no assessor name is returned). This returns the rubric's structure, not any one student's completed assessment — use get_rubric_assessment for that. Requires the manage_rubrics permission in the course, so most students cannot call this.

Input Schema

NameRequiredDescriptionDefault
includeNoRelated Canvas records to include. Use assignment_associations to retrieve association IDs for linked assignments. Canvas honours only one association scope per request; extra association values are ignored.
course_idYesThe Canvas course ID
rubric_idYesThe Canvas rubric ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / include
      Added value: +{
+  "description": "Related Canvas records to include. Use assignment_associations to retrieve association IDs for linked assignments. Canvas honours only one association scope per request; extra association values are ignored.",
+  "items": {
+    "enum": [
+      "assessments",
+      "graded_assessments",
+      "peer_assessments",
+      "associations",
+      "assignment_associations",
+      "course_associations",
+      "account_associations"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / rubric_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / rubric_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

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the authorization requirement (manage_rubrics in the course) and a non-obvious data limitation ('assessor_id-only assessment summaries (no assessor name is returned)'). It also clarifies that the payload is rubric structure, not a graded assessment, which prevents a common misfire.

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?

Four sentences, front-loaded with the core action and return fields, then routing, then option semantics, then permissions. Every sentence carries distinct information with no repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter read tool with full schema coverage and no output schema, the description covers purpose, prerequisites, the relevant include-option outcomes, and the permission gate. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining what specific include values yield beyond the bare enum — assignment_associations supplies the association IDs that submit_rubric_assessment needs, and the assessments variants return assessor_id-only summaries. It does not address the other association values (associations, course_associations, account_associations) or restate the one-scope-per-request rule, leaving a small gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get a single rubric's definition') and enumerates the returned fields (title, points_possible, criteria, rating levels). It explicitly distinguishes itself from list_rubrics and get_rubric_assessment, so an agent can separate the three sibling tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the prerequisite chain ('use list_rubrics to find the rubric_id for a course first'), names the sibling that handles the adjacent use case ('use get_rubric_assessment for that'), and adds an eligibility exclusion ('Requires the manage_rubrics permission... most students cannot call this'). Both when-to-use and when-not-to-use are covered.

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