Skip to main content
Glama

Send Message

send_message
Destructive

Sends a Canvas Inbox message to instructors or classmates using recipient IDs, with a preview-and-confirm step before delivery.

Instructions

Send a new Canvas Inbox message, e.g. to a professor or classmate. Recipients get it immediately. Get recipient IDs from find_recipients; to answer an existing thread, use reply_to_conversation. [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": {
      "recipients": "<recipients>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesMessage body text. Plain text or simple HTML.
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
subjectYesMessage subject line.
course_idNoCourse context, recommended
recipientsYesCanvas user IDs from find_recipients
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.
separate_threadsNoSend individually rather than as a group thread

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.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. Changed2 schema fields changedv1.0.2
    • addedInput schema / properties / body / description
      Added value: +"Message body text. Plain text or simple HTML."
    • addedInput schema / properties / subject / description
      Added value: +"Message subject line."
  3. First observedv1.0.1

TDQS

A4.8/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: recipients receive the message immediately, and there is a required preview/confirm_token flow with explicit user confirmation. This is important contextual detail for a non-idempotent, open-world, destructive-flagged write operation.

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?

The description is front-loaded and efficient, with useful operational details placed early. The bracketed confirmation note is longer and more procedural than the rest, but it earns its space by preventing incorrect invocation.

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 seven-parameter write tool with no output schema, the description covers the critical context: purpose, recipient source, alternative tool for replies, immediacy, and confirmation protocol. 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 already 100%, so parameter documentation is strong without the description. The description still adds useful meaning by explaining that recipient IDs come from find_recipients and by describing how confirm and confirm_token are used together after preview.

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: sending a new Canvas Inbox message, with examples of recipients. It explicitly distinguishes this from replying to an existing thread by naming reply_to_conversation, so the agent can route correctly.

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

Usage Guidelines5/5

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

It gives clear usage guidance: start a new message here, get recipient IDs from find_recipients, and use reply_to_conversation to answer an existing thread. The confirmation workflow also tells the agent exactly when and how to invoke the tool in two steps.

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