Skip to main content
Glama

Get All Grades

get_all_grades
Read-onlyIdempotent

Retrieve current and final grades for all active Canvas courses in one call, including unposted grades when available. Read-only view for checking your academic standing.

Instructions

Get your current and final grades for every active course in one call, including unposted grades where Canvas shows them. Read-only. Use get_course_grade_breakdown to see how one course's grade is calculated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_grades"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
coursesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "courses": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "code": {
      +            "type": "string"
      +          },
      +          "course": {
      +            "type": "string"
      +          },
      +          "course_id": {
      +            "type": "string"
      +          },
      +          "current_grade": {
      +            "type": "string"
      +          },
      +          "current_score": {
      +            "type": "number"
      +          },
      +          "final_grade": {
      +            "type": "string"
      +          },
      +          "final_score": {
      +            "type": "number"
      +          },
      +          "note": {
      +            "type": "string"
      +          },
      +          "term": {
      +            "type": "string"
      +          },
      +          "unposted_current_score": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "course_id",
      +          "course"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "courses"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description adds the useful nuance that unposted grades are included 'where Canvas shows them', which is behavioral context beyond annotations, but the 'Read-only' sentence is redundant and no other behavioral details (e.g., data recency, authentication) are provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the core purpose. The alternative suggestion is compact. However, the standalone 'Read-only' sentence is redundant with the annotations and does not add new information, so it slightly violates the 'every sentence earns its place' principle.

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 tool has an output schema (which explains return values) and no parameters, the description covers everything needed: what the tool returns, the scope of courses, the inclusion of unposted grades, and a pointer to the relevant alternative for grade breakdown. Nothing an agent needs in order to call it correctly is missing.

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?

The tool has zero parameters, so the baseline is 4 per the rubric. The description does not need to explain parameter meanings, and it appropriately focuses on the tool's purpose and output scope.

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 ('Get'), resource ('current and final grades for every active course'), scope ('in one call'), and data nuance ('including unposted grades where Canvas shows them'). It also distinguishes itself from the sibling get_course_grade_breakdown by naming it as the alternative for a different use case.

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?

Names an alternative (get_course_grade_breakdown) for a related but distinct need, giving clear context for when to use that tool instead. However, it does not explicitly state when not to use this tool (e.g., for unposted grades only, which could be served by get_unposted_grades) nor does it mention other grade-related siblings.

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