Skip to main content
Glama
Sign In
Canvas LMS MCP Server

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Group

create_group
Destructive

Create a group inside a group category. This is addressed by group_category_id, not by course ID: find the category with list_group_categories. The new group has no members; add them with add_group_member.

Instructions

Create a group inside a group category. This is addressed by group_category_id, not by course ID: find the category with list_group_categories. The new group has no members; add them with add_group_member.

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": {
      "group_category_id": "<group_category_id>",
      "name": "<name>"
    },
    "name": "create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the group
join_levelNoJoin policy for the group. Only affects self-joining in categories that allow multiple memberships (e.g. student-organized); for teacher-managed group sets, self-signup is a category setting.
descriptionNoDescription of the group
group_category_idYesThe Canvas group category ID to create the group in (not a course ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.19

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that the new group starts empty and how to fill it, but says nothing about who may create groups (teacher vs. student permissions), duplicate-name behavior, or whether the created group's ID is returned — meaningful gaps for a create mutation.

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?

Three short sentences, zero filler, with the addressing constraint front-loaded before the discovery and follow-up hints.

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?

With no output schema, the description should ideally say what comes back (notably the new group's ID, needed for add_group_member); it also omits permission requirements. Otherwise the creation workflow is adequately covered.

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 coverage is 100%, so the baseline is 3; the description earns a small bump for restating the category-vs-course distinction at the point of use, though it duplicates the schema's own wording. join_level's category-dependent semantics are covered by the schema, not the description.

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 ('Create a group inside a group category') and immediately disambiguates the addressing key: group_category_id, not course ID. An agent can distinguish it from create_group_category and add_group_member without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent to list_group_categories to find the required ID and to add_group_member for populating the group. That is a concrete when/how sequence plus a named alternative for membership operations.

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