Skip to main content
Glama
Sign In
Canvas LMS MCP Server

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Group Category

create_group_category
Destructive

Create a new, empty group category (group set) in a course.

Instructions

Create a new, empty group category (group set) in a course.

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>",
      "name": "<name>"
    },
    "name": "create_group_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the group category
course_idYesThe Canvas course ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.19

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint and openWorldHint, so the safety profile is carried by structured data. The description adds only the useful detail that the resulting category is 'empty' (no groups auto-created), but says nothing about who may create categories, whether duplicate names are allowed, or what happens on failure in a course without group permissions.

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?

A single short sentence with no filler; the key qualifier 'empty' is front-loaded and immediately actionable.

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?

For a two-parameter create tool with annotations present this covers the core action, but there is no output schema, so the description should mention that the created category (and its id) is returned — an agent needs that id to subsequently create groups in the new set. Permission expectations are also absent.

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 coverage is 100%: both course_id and name are fully documented in the schema. The description neither repeats nor enriches them, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a new, empty group category') and adds the Canvas synonym 'group set' plus the meaningful qualifier 'empty', which distinguishes it from a factory that also provisions groups. It does not explicitly contrast with siblings like list_group_categories or create_group, but the operation is unambiguous.

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?

The description gives no when-to-use guidance, no prerequisites (e.g. course edit permissions), and does not mention alternatives such as create_group or list_group_categories, which sit right next to it in the tool list. The agent must infer all context from the name alone.

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