Skip to main content
Glama

Mark Module Item Done

mark_module_item_done
Idempotent

Marks a Canvas module item as done to satisfy its 'mark as done' completion requirement and update the instructor progress view.

Instructions

Mark a module item as done to satisfy a 'mark as done' completion requirement. Shows in your instructor's progress view.

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>",
      "module_id": "<module_id>",
      "item_id": "<item_id>"
    },
    "name": "mark_module_item_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesModule item ID (numeric string). Get it from list_module_items.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
module_idYesModule ID (numeric string). Get it from list_modules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • 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."
    • changedInput schema / properties / item_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Module item ID (numeric string). Get it from list_module_items."
    • changedInput schema / properties / module_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Module ID (numeric string). Get it from list_modules."
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already disclose that this is a non-read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context beyond that: the action satisfies a completion requirement and is visible in the instructor's progress view. It does not state reversibility or any enrollment prerequisite, but the core side effect is disclosed.

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

Conciseness5/5

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

The description is two sentences with no wasted wording. The action and its purpose are front-loaded, and the instructor-visibility detail is secondary and useful.

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 simple three-parameter mutation, the annotations cover the safety profile and the description explains the intended effect and visibility. The main gap is that it does not explicitly contrast this tool with mark_module_item_read, but otherwise it gives enough context to invoke the tool correctly.

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%, and the schema already explains all three IDs and where to retrieve them via list_courses, list_modules, and list_module_items. The description adds no parameter-level meaning beyond the schema, so the baseline score of 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?

The description states a specific verb and resource: mark a module item as done. It also explains the intended effect, satisfying a 'mark as done' completion requirement. However, it does not explicitly distinguish this from the sibling tool mark_module_item_read.

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?

Usage is implied by the phrase 'to satisfy a mark as done completion requirement,' giving the agent a clear condition for when this tool applies. It does not provide when-not guidance or name alternatives, such as marking an item as read instead.

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