Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Outcome Group Links

list_outcome_group_links
Read-only

List all outcome links in an account or course context.

Instructions

List all outcome links in an account or course context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
context_idYesThe Canvas account ID or course ID for the context.
context_typeYesWhether to read outcome links from an account or course context.
outcome_styleNoOutcome detail level. Use "full" to include expanded outcome fields.
outcome_group_styleNoOutcome group detail level. Use "full" to include expanded outcome group fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.15
    • addedInput schema / properties / context_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / context_id / type
      Removed value: -"number"
  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. First observedv1.18.0

TDQS

C2.9/5.0
Behavior2/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 nothing beyond that: it says nothing about pagination, whether results are scoped to one level of the outcome hierarchy, or how links relate to groups and outcomes. With annotations carrying the load, a low score is still warranted because the text contributes no extra behavioral context.

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 filler or redundancy. It is efficient, though arguably too terse for a tool sitting in a dense cluster of similarly named outcome tools.

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

Completeness2/5

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

There is no output schema, and the description does not explain what an 'outcome link' contains or how it differs from outcome groups, group outcomes, or outcome alignments. For a read tool in a crowded sibling namespace, an agent would need more context to pick it confidently.

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% and all four parameters are documented in the schema, including the enum meanings for context_type, outcome_style, and outcome_group_style. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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 gives a specific verb and resource ('List all outcome links') and bounds the scope to 'an account or course context', which maps directly to the required context_type parameter. It stops short of distinguishing the tool from close siblings such as list_outcome_group_outcomes, list_outcome_group_subgroups, or get_outcome_alignments, leaving some ambiguity about what an 'outcome link' actually is.

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?

No when-to-use guidance is offered and no alternative is named. The phrase 'in an account or course context' only echoes the required context_type enum rather than telling the agent when this listing is preferable to the other outcome-group listing tools in the sibling set.

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