Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Leave Group

leave_group
Destructive

Leave a Canvas student group and remove access to its workspace; preview the action first, then confirm with the returned token to complete it.

Instructions

Leave a student group you belong to. You lose access to its workspace. [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": {
      "group_id": "<group_id>"
    },
    "name": "leave_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
group_idYesStudent group ID (numeric string). Get it from list_my_groups.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

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. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / group_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Student group ID (numeric string). Get it from list_my_groups."
  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?

With destructiveHint already true, the description adds the concrete consequence, loss of workspace access, and fully spells out the confirmation protocol: preview call, show preview, then repeat with the same arguments plus confirm and confirm_token. It also notes that apps able to ask the user directly show a confirmation instead, which is behavior no annotation conveys.

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?

It is short and front-loads the action and consequence. The bracketed confirmation block is dense but each clause earns its place by encoding the required workflow. The bracket notation is slightly awkward for a description field.

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 action with three parameters and no output schema, the description covers what is destroyed, the exact confirmation sequence, and the fallback for apps that can prompt the user. Nothing essential for 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 explains the relationship between confirm and confirm_token beyond the individual field descriptions: it says that the second call must repeat the same arguments and supply the token. It does not explain where group_id comes from beyond the schema.

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?

The description states a specific verb and resource ('Leave a student group') and adds the membership qualifier ('you belong to'), which clearly separates it from join_group and other group tools. It also states the outcome, so an agent knows the effect of the call.

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?

It gives explicit context for when to invoke: after the user confirms, and it describes a two-call preview-then-commit pattern. It does not name alternatives such as join_group or say when not to use it, so it falls short of full routing guidance.

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