Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update Appointment Group

update_appointment_group
Destructive

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

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. Changed2 schema fields changedv1.18.15
    • addedInput schema / properties / appointment_group_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / appointment_group_id / type
      Removed value: -"number"
  2. 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"
  3. 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
  4. Addedv1.18.4

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this is a state-changing operation. The description adds some behavioral context by explaining that publishing makes a draft visible and that new_appointments adds slots, but it does not describe overwrite behavior, permissions needed, or consequences for omitted fields.

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 short sentences, front-loaded with the tool's core purpose and followed immediately by the two most operationally important parameter behaviors. There is no filler or redundant restatement.

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 eight-parameter mutation tool with annotations covering destructive and open-world behavior, the description covers the two non-obvious parameters but leaves update semantics unspecified. It does not say whether omitted fields are preserved or cleared, nor does it describe authorization requirements. It is minimally adequate given the rich schema and existing safety annotations, but not complete.

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 description coverage is 100%, so the schema already documents all eight parameters, including publish, new_appointments, and appointment_group_id. The description adds only a small nuance over the schema for publish and new_appointments, so the baseline of 3 is appropriate.

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 gives a specific verb and resource: 'Update an existing appointment group.' That clearly separates it from create_appointment_group, delete_appointment_group, and get_appointment_group. It stops short of explicitly naming or routing against siblings, so it is clear but not maximally differentiated.

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?

It provides useful usage context for two parameters: publish=true for making a draft visible, and new_appointments for adding slots. However, it never states when to use this tool versus create_appointment_group, delete_appointment_group, or other update tools, and it gives no prerequisites or exclusions.

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