Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Post Group Discussion

post_group_discussion
Destructive

Preview and post a message to a Canvas group discussion so groupmates and instructors can see it.

Instructions

Post to a discussion inside a group workspace. Visible to your groupmates and instructors. [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>",
      "topic_id": "<topic_id>",
      "message": "<message>"
    },
    "name": "post_group_discussion"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
messageYesMessage text. Plain text or simple HTML.
group_idYesStudent group ID (numeric string). Get it from list_my_groups.
topic_idYesDiscussion topic ID (numeric string). Get it from list_topics.
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. Changed3 schema fields 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."
    • addedInput schema / properties / message / description
      Added value: +"Message text. Plain text or simple HTML."
    • changedInput schema / properties / topic_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Discussion topic ID (numeric string). Get it from list_topics."
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare the safety profile (destructive, non-idempotent, open-world, not read-only); the description goes well beyond that by disclosing the two-phase preview/confirm-token protocol, which is the single most important behavioral fact about this tool. It also notes a fallback for apps that can ask the user directly, and states the audience. It does not explain the destructive hint or what the confirm token's lifetime/one-time nature implies, but the critical flow is covered.

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?

Two sentences plus a bracketed note, front-loaded with purpose and audience before the mechanics. The bracketed meta-marker is awkward formatting but its content is essential and earns its place; there is no redundant wording.

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 mutating tool with no output schema and a non-obvious confirm flow, the description supplies exactly what is needed: scope, audience, and the full preview-then-confirm sequence. The remaining details (ID sourcing, message format, token provenance) are already carried by the parameter descriptions.

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 coverage is 100%, so all five parameters are already documented, and the confirmation parameters get clear descriptions in the schema. The description reinforces the confirm semantics ("call it again with the same arguments, confirm=true and that confirm_token") but adds little about group_id, topic_id, or message beyond what the schema already says. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Post to a discussion inside a group workspace") and adds the audience ("Visible to your groupmates and instructors"), which tells an agent this is a group-scoped discussion post rather than a private message or a reply. It stops short of naming the sibling it differs from, such as post_entry or reply_to_entry, so the distinction from other posting tools is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The visibility sentence implies group context, but there is no explicit when-to-use or when-not-to-use guidance relative to reply_to_entry, post_entry, or send_message. An agent must infer from sibling names alone whether a top-level post or a reply is 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