Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Select Mastery Path

select_mastery_path
Destructive

Choose a mastery path branch (conditional release) in a Canvas module to unlock its assignments; preview and confirm first because the selection may be irreversible.

Instructions

Choose which branch to follow at a mastery path (conditional release) point in a module. Unlocks that branch's assignments and may not be reversible. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course_id": "<course_id>",
      "module_id": "<module_id>",
      "item_id": "<item_id>",
      "assignment_set_id": "<assignment_set_id>"
    },
    "name": "select_mastery_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
item_idYesModule item ID (numeric string). Get it from list_module_items.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
module_idYesModule ID (numeric string). Get it from list_modules.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.
assignment_set_idYesID of the mastery path option to choose, from get_module_item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually execute. Omit or set false to get a dry-run preview first."New value: +"Set to true together with confirm_token to carry out a request you already previewed."
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed4 schema fields changedv1.1.3
    • changedInput schema / properties / assignment_set_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"ID of the mastery path option to choose, from get_module_item."
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • changedInput schema / properties / item_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Module item ID (numeric string). Get it from list_module_items."
    • changedInput schema / properties / module_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Module ID (numeric string). Get it from list_modules."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint/openWorldHint annotations, the description discloses the concrete effect ('unlocks that branch's assignments') and the irreversibility risk, plus a two-phase confirmation protocol with a one-time token. This is exactly the kind of operational context annotations cannot convey.

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?

Purpose and consequence come first, with the confirmation protocol confined to a clearly marked bracketed block. The second sentence is dense but each clause (preview, show user, re-call with same args, native-confirmation exception) carries operational weight; minor redundancy between the block and the confirm/confirm_token schema descriptions.

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?

For a destructive, non-idempotent mutation with no output schema, the description supplies consequences, reversibility, and the full safety protocol an agent needs to avoid an unrecoverable mistake. Nothing essential to correct invocation 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about how confirm and confirm_token interact across two calls ('call it again with the same arguments... and that confirm_token'), which the schema only states in isolation. It does not clarify assignment_set_id sourcing beyond the schema, hence not a 5.

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 and resource ('Choose which branch to follow at a mastery path (conditional release) point in a module'), which is unambiguous and clearly distinct from sibling module tools like get_module_item or mark_module_item_done. The parenthetical gloss of 'mastery path' as conditional release helps an agent recognize the domain concept.

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?

The bracketed block gives an explicit, actionable when/how sequence: preview first, show the user, only re-call with confirm=true and the token after a yes, and skip the pattern entirely for apps that can prompt the user natively. It does not explicitly name alternative tools (e.g., get_module_item to inspect options), but the required-parameter schema already routes to those.

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