Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Outcome Results

get_outcome_results
Read-only

Retrieve per-student learning outcome results for a Canvas course, with optional filters for specific outcomes, students, or alignment details.

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 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. 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. 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"
+]
  3. First observedv1.18.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only safety profile is covered. The description aligns with those annotations and clarifies that results are per-student, but it does not add information about pagination, response format, or hidden-outcome behavior beyond what the schema already provides.

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 one efficient sentence that front-loads the verb and resource, then flattens the optional filters. Every word earns its place; there is no redundant phrasing or repeated title information behavior.

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?

The description is adequate for making a basic call with course_id, but the absence of an output schema means the agent is not told what a per-student outcome result actually contains or how to interpret the response. It also does not clarify how to choose from the large outcome-related sibling set, leaving some ambiguity for an automated caller.

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 the schema already documents every parameter. The description paraphrases the filter axes (outcome, student, alignment) without adding meaning beyond the schema, and does not clarify the include_hidden interaction or any parameter combinations.

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?

The description uses a clear verb ('Get') and resource ('per-student outcome results for a course') and lists optional filters for outcome, student, and alignment. It does not explicitly name a sibling tool for differentiation, though 'per-student' helps distinguish it from aggregate outcome tools like get_outcome_rollups.

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?

There is no guidance about when to use this tool versus get_outcome_rollups, get_outcome_contributing_scores, or similar outcome-related siblings. The description only states what it does; it does not explain under which circumstances to prefer this tool or when a related tool would be more appropriate.

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