Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Outcome Results

get_outcome_results
Read-only

Get per-student outcome results for a course, with optional outcome, student, and alignment filters.

Instructions

Get per-student outcome results for a course, with optional outcome, student, and alignment filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idsNoOptional Canvas user IDs (pass large IDs as strings) or SIS user IDs prefixed with "sis_user_id:".
course_idYesThe Canvas course ID.
outcome_idsNoOptional outcome IDs to restrict the results.
include_hiddenNoInclude hidden outcomes when Canvas supports it.
include_alignmentsNoInclude linked alignment details in the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.18.15
    • addedInput schema / properties / course_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / course_id / type
      Removed value: -"number"
    • addedInput schema / properties / outcome_ids / items / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / outcome_ids / items / type
      Removed value: -"number"
    • changedInput schema / properties / user_ids / description
      Previous value: -"Optional Canvas user IDs or SIS user IDs prefixed with \"sis_user_id:\"."New value: +"Optional Canvas user IDs (pass large IDs as strings) or SIS user IDs prefixed with \"sis_user_id:\"."
    • addedInput schema / properties / user_ids / items / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  },
+  {
+    "pattern": "^sis_user_id:[\\s\\S]+$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / user_ids / items / type
      Removed value: -[
-  "number",
-  "string"
-]
  2. 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"
  3. Changed2 schema fields changedv1.18.8
    • removedInput schema / properties / user_ids / items / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]
    • addedInput schema / properties / user_ids / items / type
      Added value: +[
+  "number",
+  "string"
+]
  4. First observedv1.18.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the data granularity (per-student rows, optional alignment detail) which is useful given there is no output schema, but it discloses nothing about pagination, result size, permissions, or how hidden outcomes behave.

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?

A single front-loaded sentence with no wasted words; the resource and its filters come first. It is efficient, though arguably too terse to earn a top score given how many adjacent outcome tools exist.

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?

For a read-only query with full schema coverage and no output schema, the description is minimally adequate, but it omits any differentiation from the rollup/contributing-score/mastery-distribution siblings and gives no sense of return shape or pagination. An agent choosing among the outcome family is left under-informed.

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?

Schema description coverage is 100%, so every parameter is already documented in the schema; baseline is 3. The description names three of the five filter dimensions (outcome, student, alignment) but omits include_hidden and adds no format or defaulting detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get per-student outcome results for a course) plus the filter dimensions, so the agent knows exactly what is returned. However, it does not distinguish itself from the many sibling outcome tools (get_outcome_rollups, get_outcome_contributing_scores, get_outcome_mastery_distribution), leaving the agent to guess which outcome view it wants.

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

Usage Guidelines2/5

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

The description only restates the tool's shape ('with optional outcome, student, and alignment filters') without saying when to reach for it over the outcome siblings or what preconditions exist. No when-to-use, when-not-to-use, or alternative is named.

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