Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Cancel Reservation

cancel_reservation
Destructive

Cancel a booked appointment slot and notify the instructor; get the event_id from list_my_reservations and confirm the preview before finalizing.

Instructions

Cancel an appointment slot you booked. The instructor can see the cancellation. Get event_id from list_my_reservations. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

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": {
      "event_id": "<event_id>"
    },
    "name": "cancel_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
event_idYesCalendar event ID (numeric string). Get it from list_calendar_events or list_my_reservations.
cancel_reasonNoOptional reason shown to the instructor.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually execute. Omit or set false to get a dry-run preview first."New value: +"Set to true together with confirm_token to carry out a request you already previewed."
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv1.1.3
    • addedInput schema / properties / cancel_reason / description
      Added value: +"Optional reason shown to the instructor."
    • changedInput schema / properties / event_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Calendar event ID (numeric string). Get it from list_calendar_events or list_my_reservations."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one real behavioral fact beyond them — 'The instructor can see the cancellation' — plus the preview/confirm choreography. However, the confirm mechanics are also documented in the schema, and it says nothing about failure modes (already cancelled, past event, missing permission) for a destructive, non-idempotent mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are crisp and front-loaded, and the bracketed confirmation block is dense but necessary operational detail. It is somewhat verbose relative to the core action and could be tightened, but nothing is truly wasted.

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?

For a destructive, non-idempotent mutation with no output schema, the definition covers the action, the ID source, the side effect on the instructor, and the full confirmation protocol. The remaining shortfall is lack of edge-case behavior and no explicit contrast with delete_calendar_event among the many calendar-related siblings.

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 explains event_id, confirm, confirm_token and cancel_reason; baseline 3 applies. The description reinforces the confirm flow and the event_id source but adds no new meaning beyond the schema text, and never mentions cancel_reason or its visibility to the instructor.

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 plus resource — 'Cancel an appointment slot you booked' — which scopes it to appointment-slot reservations rather than arbitrary calendar events. It does not explicitly name the nearest sibling, delete_calendar_event, so an agent must still infer the boundary between cancelling a booked appointment and deleting a calendar event.

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

Usage Guidelines4/5

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

It states where to source event_id ('Get event_id from list_my_reservations') and spells out the exact two-step preview-then-confirm protocol, which is genuinely actionable guidance. The gap is that it never says when to prefer this over delete_calendar_event or what to do if the slot is already cancelled.

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