Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Submit Assignment Text

submit_assignment_text
Destructive

Submit text to a Canvas online text-entry assignment as a real submission attempt. Preview first, then confirm to send your exact content to the instructor.

Instructions

Submit text for an online text-entry assignment, exactly as given; the tool never writes content for you. Your instructor sees it and it counts as a submission attempt. [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>",
      "assignment_id": "<assignment_id>",
      "body": "<body>"
    },
    "name": "submit_assignment_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe submission text (HTML allowed)
commentNoOptional comment to the instructor
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
assignment_idYesAssignment ID (numeric string). Get it from list_assignments or list_upcoming_assignments.
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. Changed2 schema fields changedv1.1.3
    • changedInput schema / properties / assignment_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Assignment ID (numeric string). Get it from list_assignments or list_upcoming_assignments."
    • 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."
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false; the description adds real value on top by disclosing the user-visible consequences (instructor sees it, counts as an attempt) and the mandatory two-call confirmation flow with a one-time token. It does not say whether a second submission overwrites the first or whether re-submission is even permitted, which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The substance is dense and front-loaded, but the bracketed "[NEEDS CONFIRMATION: ...]" marker reads as an unresolved editorial artifact inside the agent-facing text, which hurts readability and may be mistaken for a literal instruction. The three core assertions (exact text, instructor visibility, attempt counting) are well placed before the procedure.

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

Completeness4/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 definition covers the consequence and the confirmation mechanism, which is the critical path to calling it correctly. It stops short of describing what the preview response contains (beyond implying a confirm_token) or what a successful submission returns.

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% and the schema already documents body, comment, confirm and confirm_token individually, including where to obtain course_id and assignment_id. The description restates the confirm/confirm_token usage but adds only the sequencing detail ("same arguments"), so the baseline of 3 is appropriate.

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 ("Submit text for an online text-entry assignment") and implicitly separates itself from the submit_assignment_url / submit_assignment_file siblings by naming the assignment type it applies to. It also states the negative scope plainly: "the tool never writes content for you."

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?

Explains the operational context clearly: content is submitted exactly as given, the instructor sees it, and it consumes a submission attempt. The preview-then-confirm protocol is spelled out step by step. What's missing is an explicit pointer to the sibling tools for file or URL submissions, which is left to inference from "text-entry assignment".

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