Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Post Submission Comment

post_submission_comment
Destructive

Posts a comment on your own assignment submission, optionally with uploaded files, so your instructor can see it.

Instructions

Post a comment on your own submission for an assignment, optionally with files attached. Your instructor sees it. To attach a file, upload it first with upload_comment_attachment. [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>",
      "comment": "<comment>"
    },
    "name": "post_submission_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesComment text, visible to your instructor.
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
file_idsNoOptional file IDs returned by upload_comment_attachment, to attach to this comment.
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. Changed4 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."
    • addedInput schema / properties / comment / description
      Added value: +"Comment text, visible to your instructor."
    • 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."
    • addedInput schema / properties / file_ids
      Added value: +{
      +  "description": "Optional file IDs returned by upload_comment_attachment, to attach to this comment.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  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 already flag destructiveHint=true, openWorld=true and idempotent=false, so safety framing is partly covered. The description adds genuinely non-obvious behavior: the comment is visible to the instructor (publication/notification side effect) and a preview-then-confirm handshake with a one-time confirm_token. It stops short of explaining why the call is destructive or what a repeated call does, and the '[NEEDS CONFIRMATION: ...]' bracket reads like an unresolved internal note rather than clean documentation.

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 first two sentences are tight and front-loaded, but the confirmation paragraph is long, bracketed, and seeded with placeholder-style text ('[NEEDS CONFIRMATION:') that reads as an unfinalized TODO. That block is essential information presented in a way that is harder to parse than a plain two-sentence instruction would be.

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 6-parameter write tool with no output schema and full schema coverage, the description covers audience, attachment prerequisites, and the confirmation handshake — the things an agent must know to call it correctly. The only real gap is that it says nothing about the result of a successful call (e.g., whether a comment object or ID comes back), which matters because no output schema exists.

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 description coverage is 100%, so all six parameters (including confirm and confirm_token) are already documented in the schema, establishing the baseline of 3. The description's file-attachment sentence and confirm flow restate what the schema already says via file_ids ('returned by upload_comment_attachment') and confirm ('carry out a request you already previewed'), adding little beyond field-level documentation.

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?

Specific verb + resource + scope: 'Post a comment on your own submission for an assignment,' with the audience stated ('Your instructor sees it'). It distinguishes itself from upload_comment_attachment (prerequisite) and from discussion tools by anchoring on 'submission,' though it does not explicitly name the nearest alternative (e.g., post_entry / reply_to_entry) the way a 5 would.

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?

Gives concrete sequencing guidance: to attach files, call upload_comment_attachment first and pass the returned IDs. The confirmation/preview flow also tells the agent exactly how to invoke it safely. No explicit when-not-to-use guidance, and the bracketed 'NEEDS CONFIRMATION' phrasing leaves it ambiguous whether the two-step flow is mandatory or environment-dependent.

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