Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_rubric

Read-only

Retrieve rubric criteria, ratings, and points for a Canvas course using rubric ID or assignment ID.

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).

    Args:
        course_identifier: Course code or Canvas ID
        rubric_id: Canvas rubric ID (direct lookup)
        assignment_id: Canvas assignment ID (get rubric attached to assignment)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
rubric_idNo
assignment_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description consistently describes a read operation. It adds behavioral context by detailing parameter precedence and lookup methods, which goes beyond what annotations provide.

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 extremely concise, using three sentences plus a labeled Args list. Every sentence adds value, with the main purpose front-loaded.

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?

Given the presence of an output schema, the description needs only to explain input and behavior. It covers purpose, parameter selection logic, and parameter meanings completely.

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

Parameters5/5

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

Despite 0% schema description coverage, the description fully explains each parameter's purpose and format: course_identifier as course code or ID, rubric_id for direct lookup, assignment_id for attached rubric. This adds significant value over the raw schema.

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 tool retrieves detailed rubric criteria, ratings, and points. It distinguishes itself from sibling tools like list_rubrics (listing) and create_rubric (creation) by focusing on retrieval with specific identifiers.

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

Usage Guidelines4/5

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

The description explains when to use rubric_id vs assignment_id, including precedence when both are provided. It does not explicitly mention when not to use the tool, but the guidance is sufficient for correct invocation.

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