HairDora Salon Scheduling

List stylists who take appointments

list_providers

Read-onlyIdempotent

Use this when someone asks which stylists or hairdressers work at their salon or can be booked, or which stylist to book a client with. Returns up to 100 hairdresser ids and display names from the organization that owns the salon (no contact details or schedules). Not for stylists' days off.

Input Schema

Name	Required	Description	Default
`salonId`	Yes	Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters)

Output Schema

Name	Required	Description
`count`	Yes
`status`	Yes
`hasMore`	Yes
`providers`	Yes	Ids and display names of organization members with the hairdresser role; roles are organization-wide, not per salon. The ids are the ones the salon's public booking page already shows. Contact details, avatar URLs, role records, schedules and organization data are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 4, 2026

changedOutput schema / properties / providers / description

Previous value: -"Display names of organization members with the hairdresser role; roles are organization-wide, not per salon. Staff ids, contact details, avatar URLs, role records, schedules and organization data are excluded."New value: +"Ids and display names of organization members with the hairdresser role; roles are organization-wide, not per salon. The ids are the ones the salon's public booking page already shows. Contact details, avatar URLs, role records, schedules and organization data are excluded."

addedOutput schema / properties / providers / items / properties / id

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[0-9a-f]{24}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The id book_appointment takes in providerIds"
+}

changedOutput schema / properties / providers / items / required

Previous value: -[
-  "displayName"
-]New value: +[
+  "id",
+  "displayName"
+]

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / salonId / description

Previous value: -"Salon id returned by list_salons (24 lowercase hex characters)"New value: +"Id of one of the user's salons, as the salon list returns it (24 lowercase hex characters)"

addedOutput schema / properties / providers / description

Added value: +"Display names of organization members with the hairdresser role; roles are organization-wide, not per salon. Staff ids, contact details, avatar URLs, role records, schedules and organization data 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 this is a safe, idempotent, closed read. Beyond that, the description discloses the 100-result cap and the field scope of the payload (ids and display names only, no contacts or schedules), which are real behavioral limits an agent should know before relying on the output.

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?

Three short sentences, front-loaded with the usage trigger and then the return shape and exclusion. Minor redundancy between 'stylists' and 'hairdressers' and between 'work at' and 'can be booked', but nothing wasteful enough to impede scanning.

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?

Given an output schema, rich annotations, and a single 100%-documented parameter, the description fills the remaining gaps: who the tool is for, what it returns, and what it does not cover. Only the absence of an explicit pointer to the availability sibling keeps it from being fully complete.

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?

The single salonId parameter is already fully documented in the schema, including format and origin. The description adds only mild extra framing ('from the organization that owns the salon'), which clarifies scoping but does not add syntax or validation meaning beyond the schema.

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 ('Returns up to 100 hairdresser ids and display names') and pins the scope to the organization owning the salon. It is clearly distinguishable from schedule-oriented siblings like get_salon_availability because it explicitly says 'no contact details or schedules'.

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?

Gives concrete trigger phrasing ('when someone asks which stylists or hairdressers work at their salon or can be booked') and an explicit exclusion ('Not for stylists' days off'). It stops short of naming the alternative tool for availability, so the agent must infer the routing rather than being told directly.

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?