Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Reserve Appointment Slot

reserve_appointment_slot
Destructive

Book an instructor's office hours or advising time slot so the instructor sees your reservation; get slot IDs from get_appointment_group and cancel with cancel_reservation.

Instructions

Book an office hours or advising time slot. The instructor sees the booking. Get slot IDs from get_appointment_group; cancel with cancel_reservation. [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": {
      "appointment_id": "<appointment_id>"
    },
    "name": "reserve_appointment_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
commentsNoOptional note for the instructor, e.g. what you want to discuss.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.
appointment_idYesTime slot ID from get_appointment_group

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. Changed1 schema field changedv1.1.3
    • addedInput schema / properties / comments / description
      Added value: +"Optional note for the instructor, e.g. what you want to discuss."
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds material context beyond them: the instructor sees the booking (side-effect visibility) and the call is two-phase, so the first invocation is a preview that must not be treated as a real booking. That confirm-token protocol is the key behavioral fact an agent needs and it is not discoverable from the annotations alone.

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?

Front-loaded with the one-line purpose, then prerequisites, then the confirmation protocol — a sensible order. The bracketed '[NEEDS CONFIRMATION: ...]' block is dense and reads like internal metadata rather than prose, but every sentence carries real information, so the minor formatting awkwardness costs only a point.

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 booking tool with no output schema, the description covers prerequisites, the two-step confirm flow, side effects, and the cancellation sibling. It does not say what comes back after a successful booking (confirmation identifier, slot details) or what happens if the slot was taken in between, which are the remaining gaps.

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 an extra point by explaining the relationship between the otherwise cryptic confirm and confirm_token parameters (same arguments + confirm=true + the one-time token from the preview). It still says nothing about appointment_id validity beyond pointing at get_appointment_group, which the schema already covers.

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 ('Book an office hours or advising time slot') and immediately differentiates from siblings by naming the source of IDs (get_appointment_group) and the undo path (cancel_reservation). An agent can tell exactly what this does and what it does not do 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?

Gives explicit prerequisites (slot IDs come from get_appointment_group), an explicit alternative for the opposite operation (cancel_reservation), and a step-by-step when-to-call protocol: preview first, show it to the user, call again only after 'yes' with confirm=true and the token. Nothing about selection is left to inference.

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