Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Outcome Contributing Scores

get_outcome_contributing_scores
Read-only

Fetch assignment or quiz scores that contributed to a specific outcome for one or more students in a Canvas course.

Instructions

Get assignment or quiz scores that contributed to a specific outcome for one or more students in a course.

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_idYesThe Canvas outcome ID.
only_assignment_alignmentsNoLimit results to assignment alignments only.
show_unpublished_assignmentsNoInclude unpublished assignments in the contributing score results.

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.4/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 only the scoping fact that results are scores that 'contributed' to a specific outcome; it does not disclose pagination, defaults for unpublished assignments, or response shape. This is adequate but not strongly additive beyond purpose.

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 a single sentence with no filler, front-loading the verb and resource. It earns its place without restating the tool name or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only retrieval tool with fully documented schema parameters and clear required IDs, the description is reasonably complete for an agent to invoke it correctly. Minor gaps remain around return structure and pagination, and there is no explicit sibling differentiation, but these are not critical for basic invocation.

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?

All five parameters are documented in the schema, so the baseline is 3. The description's 'assignment or quiz scores' phrasing loosely maps to the optional filters but adds no semantic detail beyond what the schema already 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?

The description names a specific resource ('assignment or quiz scores that contributed to a specific outcome') with a clear verb and scoping to one or more students in a course. It distinguishes itself from outcome-related siblings like get_outcome_rollups and get_outcome_alignments, though it does not explicitly name them.

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 the many outcome-related siblings such as get_outcome_results, get_outcome_rollups, or get_outcome_alignments. The description implies a retrieval use case but provides no conditions, exclusions, or alternatives.

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