Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Rubric

get_rubric
Read-only

Retrieve detailed Canvas rubric criteria, ratings, and points by rubric ID or assignment ID to understand grading expectations and evaluate assignments.

Instructions

Get detailed rubric criteria, ratings, and points.

Accepts either rubric_id or assignment_id (at least one required). If both provided, uses rubric_id (more specific).

Input Schema

NameRequiredDescriptionDefault
rubric_idNoCanvas rubric ID (direct lookup)
assignment_idNoCanvas assignment ID (get rubric attached to assignment)
course_identifierYesCourse code or Canvas ID

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. Changed11 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / assignment_id / description
      Added value: +"Canvas assignment ID (get rubric attached to assignment)"
    • 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 / rubric_id / description
      Added value: +"Canvas rubric ID (direct lookup)"
    • removedInput schema / properties / rubric_id / title
      Removed value: -"Rubric Id"
    • removedInput schema / title
      Removed value: -"get_rubricArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_rubricOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds the important one-of input constraint and precedence rule, but it does not disclose error behavior, permissions, or other operational traits beyond what annotations and schema imply.

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 short, front-loaded, and contains no filler. Each sentence contributes either return-content detail or an important input constraint.

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

Completeness4/5

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

For a simple read-only rubric retrieval tool, the description covers what is returned and resolves the main ambiguity in choosing rubric_id versus assignment_id. It does not mention sibling alternatives, but the schema and annotation otherwise provide sufficient context.

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 individual parameter meanings are already documented. The description adds meaningful cross-parameter semantics: either rubric_id or assignment_id must be supplied, and rubric_id wins when both are present.

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 states a specific verb and resource: 'Get detailed rubric criteria, ratings, and points.' It does not explicitly distinguish this tool from nearby siblings such as get_rubric_assessment or list_rubrics, so it is clear but lacks sibling differentiation.

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?

It explains input selection rules for rubric_id versus assignment_id, including that at least one is required and rubric_id takes precedence. However, it gives no guidance on when to use this tool instead of alternatives like list_rubrics or get_rubric_assessment.

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