Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Grading Standards

list_grading_standards
Read-only

Get grading standards for a course or account. Use course_id for course standards, account_id for account-level (admin). Returns ids, titles, contexts, and grading schemes.

Instructions

List grading standards available in a course or account context. Provide either course_id (to see standards scoped to a course) or account_id (to see account-level standards, requires admin access). Returns an array of grading standard objects, each with an id, title, context, and grading_scheme array of { name, value } entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idNoCourse ID to list standards for (mutually exclusive with account_id)
account_idNoAccount ID to list standards for (mutually exclusive with course_id; requires admin)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Addedv1.18.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, covering safety. The description adds valuable behavioral context: the return structure (array of objects with specific fields) and the access requirement for account-level standards. This exceeds 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?

Two sentences, front-loaded with the primary action, and no wasted words. The purpose, parameter usage, and return format are all covered efficiently.

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?

Complete for a read-only list operation with no output schema. The description explains the return format and parameter semantics, leaving nothing essential missing. Pagination is not needed here, and annotations cover safety.

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% with descriptions for both parameters, but the description adds functional meaning by explaining what each parameter does (course-scoped vs account-level standards). This goes beyond the schema's mutual-exclusivity and admin notes, giving agents a clearer mental model.

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 ('List') and resource ('grading standards') with clear context distinction between course and account scopes. The description clearly differentiates this from other tools by defining its exact purpose and output format.

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?

Provides clear guidance on when to use each parameter (course_id vs account_id) and notes the admin requirement for account-level access. While it doesn't explicitly name alternatives, the sibling list shows no competing list tool, so the context is sufficient.

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