Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Appointment Group

update_appointment_group
Destructive

Modify an existing appointment group by changing title, description, location, or context. Publish a draft group or add new appointment time slots.

Instructions

Update an existing appointment group. Use publish=true to make a draft group visible to participants, or add new time slots via new_appointments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew title
publishNoSet to true to publish the group
descriptionNoNew description
context_codesNoUpdate context associations
location_nameNoLocation name
location_addressNoLocation address
new_appointmentsNoNew time slots to add as [start_at, end_at] pairs
appointment_group_idYesThe appointment group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed3 schema fields changedv1.18.5
    • changedInput schema / properties / new_appointments / items / items
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "string"
-  }
-]New value: +{
+  "type": "string"
+}
    • addedInput schema / properties / new_appointments / items / maxItems
      Added value: +2
    • addedInput schema / properties / new_appointments / items / minItems
      Added value: +2
  3. Addedv1.18.4

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already signal destructiveHint=true and openWorldHint=true; the description does not contradict them. It adds useful nuance by explaining that publish=true makes a draft group visible to participants, but it does not disclose side effects of updating existing fields or whether this is a partial or full update.

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?

Two sentences, front-loaded with the core operation, with no filler or redundant restatement of the schema. Both sentences earn their place by adding behaviorally useful context.

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 an update tool with 8 parameters and no output schema, the description provides a workable starting point but leaves several questions open: whether unspecified fields are preserved or cleared, what the response contains, and whether publishing is irreversible. The detailed schema compensates partially, but the operational semantics remain incomplete.

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?

The input schema already provides 100% parameter coverage, so the baseline is 3. The description adds some meaning for publish (visibility to participants) and new_appointments (adding slots), but it does not meaningfully enrich the other six parameters beyond what the schema already says.

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 uses a clear verb-resource pair ('Update an existing appointment group') that immediately identifies the action and scope. It distinguishes from create/delete siblings by emphasizing 'existing', though it doesn't explicitly name those sibling alternatives.

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?

The description gives guidance on when to use specific parameters ('Use publish=true... or add new time slots via new_appointments'), but does not explicitly say when to choose this tool over create_appointment_group or delete_appointment_group. Usage context is implied rather than stated.

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