list_rubricsRetrieve all rubrics for a Canvas course by providing its course ID. Use this to view available grading criteria and align assessment tools.
List all rubrics in a course.
| Name | Required | Description | Default |
|---|---|---|---|
| course_id | Yes | The Canvas course ID |
Changes observed during successful MCP inspections.
v1.18.11Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v1.18.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety and scope. The description adds no further behavioral context (e.g., pagination, ordering, or permission requirements), but it does not contradict the annotations. Since the annotations carry the load, a neutral score is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with zero waste. It directly states the action, resource, and scope, achieving maximum conciseness without sacrificing clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one required parameter and no output schema, the description is nearly complete. It does not mention potential limitations like pagination or result ordering, but these are not essential for a basic list call. The tool is simple enough that the description suffices.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description for course_id is 100% covered ('The Canvas course ID'), so the description adds no additional meaning. The single parameter is fully documented by the schema, making this baseline 3 acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'List all rubrics in a course' is specific, stating a clear verb (list), resource (rubrics), and scope (in a course). It distinguishes itself from siblings like get_rubric (which implies fetching a single rubric) and create_rubric (which creates). The purpose is unambiguous and immediately actionable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for listing all rubrics but provides no explicit guidance on when to choose this over get_rubric or create_rubric. There is no mention of alternatives or exclusions, leaving the agent to infer context from the sibling list. Adequate for a simple list operation, but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.