Skip to main content
Glama

create_assignment

Create a new assignment in a Canvas course by specifying course ID, name, due dates, grading type, and submission options.

Instructions

Create a new assignment in a course.

    Args:
        course_identifier: Course code or Canvas ID
        name: Assignment name/title
        description: HTML description
        submission_types: Comma-separated types (online_text_entry, online_url, online_upload, discussion_topic, none, on_paper, external_tool)
        due_at: Due date in ISO 8601 format
        unlock_at: Available date in ISO 8601 format
        lock_at: Lock date in ISO 8601 format
        points_possible: Maximum points
        grading_type: One of: points, letter_grade, pass_fail, percent, not_graded
        published: Whether to publish immediately (default: False)
        assignment_group_id: Assignment group ID
        peer_reviews: Enable peer reviews
        automatic_peer_reviews: Auto-assign peer reviews
        allowed_extensions: Comma-separated file extensions (e.g., "pdf,docx,txt")
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
nameYes
descriptionNo
submission_typesNo
due_atNo
unlock_atNo
lock_atNo
points_possibleNo
grading_typeNo
publishedNo
assignment_group_idNo
peer_reviewsNo
automatic_peer_reviewsNo
allowed_extensionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It does not mention side effects, authentication requirements, rate limits, or error handling (e.g., what happens if the course doesn't exist). The description focuses solely on parameter descriptions.

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 description is adequately structured with an Args block, but it is lengthy due to listing all 14 parameters. While no information is redundant, the verbosity could be trimmed by grouping similar parameters (e.g., date-related). It lacks a concise summary sentence at the start.

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?

Given the complexity (14 parameters, no annotations, 0% schema coverage), the description covers parameter meanings but omits the return value structure (despite having an output schema). It also does not specify behavior when optional fields are omitted. Overall, it meets minimum requirements but has gaps.

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 description coverage is 0%, so the description must compensate. It provides meaningful explanations for each parameter, such as 'Course code or Canvas ID' for course_identifier and ISO 8601 format for dates. This adds significant value over the raw schema titles.

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 clearly states the tool creates an assignment in a course, with a specific verb and resource. However, it does not differentiate from sibling tools like 'update_assignment' or 'list_assignments', missing an opportunity to clarify when to use this tool over others.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or situations where it should not be used. The description only explains the action, leaving the agent to infer context from sibling tool names.

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