HairDora Salon Scheduling

List salon appointments

list_appointments

Read-onlyIdempotent

Use this when someone asks how many appointments are booked on a day or in a period, how many were canceled or no-shows, when a client is booked, or which bookings a stylist has. Returns appointments across all the user's salons, or just one, with id, client, salon and stylist ids, times and status for any date window, latest first, up to 100. Not for the services inside an appointment.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of appointments to return (default 20, maximum 100)
`endTime`	No	Only appointments ending before this ISO 8601 time
`salonId`	No	Only appointments at this salon, by an id from the user's salon list; every salon when absent
`clientId`	No	Only appointments of this client, by an id from the client list
`startTime`	No	Only appointments starting at or after this ISO 8601 time

Output Schema

Name	Required	Description
`count`	Yes
`hasMore`	Yes
`appointments`	Yes	Bookings, latest start first. Free-text notes, reminders, contact details, organization data and payment details are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 4, 2026

addedOutput schema / properties / appointments / items / properties / lastEditTime

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 32,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Version to pass as expectedLastEditTime when moving or cancelling it"
+}

addedOutput schema / properties / appointments / items / properties / providerIds

Added value: +{
+  "description": "Stylists booked on it, as list_providers ids",
+  "items": {
+    "pattern": "^[0-9a-f]{24}$",
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

changedOutput schema / properties / appointments / items / required

Previous value: -[
-  "id",
-  "clientId",
-  "salonId",
-  "startTime",
-  "endTime",
-  "status"
-]New value: +[
+  "id",
+  "clientId",
+  "salonId",
+  "providerIds",
+  "startTime",
+  "endTime",
+  "status",
+  "lastEditTime"
+]

Changed3 schema fields changedSep 28, 2026

changedInput schema / properties / clientId / description

Previous value: -"Filter by a client id returned by list_clients"New value: +"Only appointments of this client, by an id from the client list"

changedInput schema / properties / salonId / description

Previous value: -"Filter by a salon id returned by list_salons"New value: +"Only appointments at this salon, by an id from the user's salon list; every salon when absent"

addedOutput schema / properties / appointments / description

Added value: +"Bookings, latest start first. Free-text notes, reminders, contact details, organization data and payment details are excluded."

First observedSep 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds genuine value beyond that by disclosing scope (all of the user's salons unless one is specified), ordering (latest first) and a hard ceiling (up to 100). It does not mention pagination or what happens when more than 100 matches exist, which is the main remaining behavioral gap.

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?

Two tight sentences plus a short exclusion clause, front-loaded with "Use this when" so the trigger condition is the first thing read. Nearly every phrase earns its place; the only wasted content is the stylist-booking example, which points at a filter the tool cannot apply.

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 read-only list tool with a full output schema, the description covers scope, ordering, cap and the return fields an agent needs to plan a follow-up call. The gap is the phantom stylist filter and the absence of any note on truncation when a date window exceeds 100 results.

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 baseline is 3 and the description mostly restates what the schema documents (date window, salon scoping, client, limit). It does introduce a mismatch: "which bookings a stylist has" implies a stylist filter, but no stylistId parameter exists in the schema, so that use case is unachievable as described.

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 (list appointments) and immediately bounds the scope: counts per day/period, cancellations and no-shows, a client's bookings, a stylist's bookings. It also carves out a clear non-purpose ("Not for the services inside an appointment"), which separates it from get_appointment and list_services without the agent needing to open either schema.

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?

The opening clause enumerates concrete user questions that select this tool (how many booked, how many canceled/no-show, when a client is booked), which is strong when-to-use guidance. The exclusion sentence gives one when-not case, but it never names the sibling to use instead (get_appointment for a single booking, list_calendar_events for calendar entries), so routing against the other 20 tools is left partly to inference.

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

All HairDora Salon Scheduling tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?