Skip to main content
Glama

List Appointment Groups

list_appointment_groups
Read-onlyIdempotent

Find bookable appointment groups such as office hours or advising slots and view open times. Use the results to choose a slot and reserve it.

Instructions

List appointment groups you can sign up for, such as office hours or advising slots, with open time slots. Read-only. Book a slot with reserve_appointment_slot.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_appointment_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
limitNoMaximum number of items to return (one page of results). Smaller is faster.
scopeNo"reservable" (default: groups you can still book) or "manageable".
include_pastNoIf true, also include appointment groups whose slots are in the past.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum number of items to return (one page of results). Smaller is faster.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed2 schema fields changedv1.0.2
    • addedInput schema / properties / include_past / description
      Added value: +"If true, also include appointment groups whose slots are in the past."
    • addedInput schema / properties / scope / description
      Added value: +"\"reservable\" (default: groups you can still book) or \"manageable\"."
  3. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description's "Read-only." adds nothing new. It contributes one useful behavioral fact — that results carry open time slots (i.e., filtering to still-bookable groups) — but says nothing about pagination behavior, default result ordering, or what happens when no groups are available.

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 purpose and ending with the constructive next action. Every clause carries information; nothing is redundant filler.

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 four-optional-parameter, no-required-argument list tool with no output schema, the description covers what it returns and how to act on it. The remaining gap is the organizer-facing "manageable" scope, which an agent would only discover by reading the schema.

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 page, limit, scope and include_past are already fully documented; baseline is 3. The description adds no meaning beyond the schema and arguably narrows it, since its "you can sign up for" framing does not acknowledge the "manageable" scope option.

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?

The description gives a specific verb and resource ("List appointment groups") plus concrete examples of what those groups are (office hours, advising slots) and the defining property (open time slots). It is clearly distinguishable from siblings like get_appointment_group (single group detail) or list_my_reservations (the user's bookings).

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 explicitly routes the follow-up action: "Book a slot with reserve_appointment_slot." That gives a clear use-then-next-step context. It does not, however, mention when to prefer get_appointment_group or list_my_reservations, nor that the schema's "manageable" scope exists for organizer-style listing, which the description's sign-up framing omits.

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