Skip to main content
Glama

acuity-scheduling

by io.usefulapi

List appointments

acuity_list_appointments
Read-only

List appointments scheduled on the account, with optional filters. Acuity REST: GET /appointments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoMax appointments to return.
emailNoFilter by client email.
maxDateNoOnly appointments on/before this date (YYYY-MM-DD or ISO datetime).
minDateNoOnly appointments on/after this date (YYYY-MM-DD or ISO datetime).
canceledNoIf true, return canceled appointments (default false).
lastNameNoFilter by client last name.
directionNoSort order by datetime. ASC (default) or DESC.
firstNameNoFilter by client first name.
calendarIDNoFilter to a specific calendar id.
appointmentTypeIDNoFilter to a specific appointment type id.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds little beyond confirming it's a read operation. No additional behavioral traits disclosed.

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 verb, no waste. Efficiently communicates purpose and mentions the REST endpoint.

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?

Given 10 parameters all documented in schema and no output schema, the description is adequate but doesn't explain return values or pagination beyond the max parameter.

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%, and the description does not add meaning beyond what's already in the schema. Baseline score 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 clearly states the tool lists appointments and mentions optional filters, but does not explicitly differentiate from sibling tools like 'acuity_get_appointment' for single appointments.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., get_appointment for a single appointment). The description only states what it does without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All acuity-scheduling toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool targets a distinct resource and action (appointments, clients, calendars, etc.) with clear naming and no overlapping functionality.

Naming Consistency5/5

All tools follow the consistent pattern 'acuity_<verb>_<noun>' with uniform verb choices (list, get, create, cancel, reschedule) and proper pluralization.

Tool Count5/5

18 tools cover the essential aspects of a scheduling system (availability, appointments, clients, calendars, etc.) without being excessive or insufficient.

Completeness4/5

Core scheduling operations are well covered, but missing update and delete for clients, and read-only access to other entities (e.g., appointment types, blocks) may limit full lifecycle management.

Resources