Skip to main content
Glama

create_module

Add a new module to a Canvas course, specifying name, position, unlock date, prerequisites, and publication status.

Instructions

Create a new module in a course.

    Args:
        course_identifier: Course code or Canvas ID
        name: Module name
        position: Position in module list (1-indexed)
        unlock_at: Unlock date/time (ISO 8601)
        require_sequential_progress: Students must complete items in order
        prerequisite_module_ids: Comma-separated module IDs that must be completed first
        published: Whether the module is published (default: True)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
nameYes
positionNo
unlock_atNo
require_sequential_progressNo
prerequisite_module_idsNo
publishedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It indicates creation but does not mention permissions, what happens on duplicate modules, or return value expectations despite an output schema being present.

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 with a clear purpose sentence and then lists parameters in a structured format. It is reasonably concise but the list could be slightly tighter.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all parameters adequately but omits behavioral context (e.g., return value, side effects, permission requirements). Given the presence of an output schema, this is acceptable but not fully sufficient.

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?

The description provides clear inline explanations for each parameter (e.g., 'Course code or Canvas ID', 'Position in module list (1-indexed)'), adding meaningful context beyond the schema's titles and types. With 0% schema description coverage, this is valuable.

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 clearly states 'Create a new module in a course' with a specific verb and resource. It is easily distinguishable from sibling tools like update_module or add_module_item.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., update_module) or any prerequisites. The description only lists parameters without contextual usage advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vishalsachdev/canvas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server