Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

associate_rubric

Destructive

Link an existing rubric to a course assignment by specifying course, rubric, and assignment IDs, and optionally configure grading use or bookmark purpose.

Instructions

Associate an existing rubric with an assignment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
purposeNoAssociation purpose: grading, bookmark (default: grading)grading
rubric_idYesID of the rubric to associate
assignment_idYesID of the assignment to associate with
use_for_gradingNoUse rubric for grade calculation (default: False)
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  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. Changed15 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / assignment_id / description
      Added value: +"ID of the assignment to associate with"
    • 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 / purpose / description
      Added value: +"Association purpose: grading, bookmark (default: grading)"
    • removedInput schema / properties / purpose / title
      Removed value: -"Purpose"
    • addedInput schema / properties / rubric_id / description
      Added value: +"ID of the rubric to associate"
    • removedInput schema / properties / rubric_id / title
      Removed value: -"Rubric Id"
    • addedInput schema / properties / use_for_grading / description
      Added value: +"Use rubric for grade calculation (default: False)"
    • removedInput schema / properties / use_for_grading / title
      Removed value: -"Use For Grading"
    • removedInput schema / title
      Removed value: -"associate_rubricArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"associate_rubricOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.3.0

TDQS

C2.9/5.0
Behavior1/5

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

The description adds no behavioral context beyond the annotations. Annotations already indicate destructive and non-idempotent behavior, but the description does not explain what happens on conflict, permission requirements, or side effects. No extra transparency is provided.

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 a single, clear, and concise sentence. It uses straightforward language without unnecessary detail, making it easy to parse.

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?

The description is minimal but covers the core action. It does not mention outcomes, such as whether the association overwrites existing data or returns a confirmation, but given the simple nature of the tool and the presence of annotations, it is adequate though not rich.

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?

The schema descriptions for all parameters are complete and precise. The tool description does not add any additional meaning beyond what the schema already conveys. Since schema coverage is 100%, the baseline of 3 is appropriate.

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?

The description clearly states the action: associating an existing rubric with an assignment. The verb 'associate' is specific and distinguishes this tool from creation or listing tools like create_rubric or list_rubrics.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, scenarios (e.g., when an association already exists), or why one might prefer this over creating a new rubric.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vishalsachdev/canvas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server