HairDora Salon Scheduling

Look up salon clients

list_clients

Read-onlyIdempotent

Use this when someone asks who their clients are, or needs a client's id to book them or to look up their appointments, payments or quotes. Returns up to 100 clients (20 by default) across all the user's salons or one, with id, name, salon and last edit time, optionally only those whose name matches. Not for a client's email, phone or notes.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of clients to return (default 20, maximum 100)
`search`	No	Only clients whose name contains these words, in any order, ignoring case and accents
`salonId`	No	Only clients of this salon, by an id from the user's salon list; every salon when absent

Output Schema

Name	Required	Description
`count`	Yes
`clients`	Yes	Clients with the ids needed to look up their bookings, payments and quotes. Email, phone, address, operator notes, service and colour history, organization data and other profile fields are excluded.
`hasMore`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

addedInput schema / properties / search

Added value: +{
+  "description": "Only clients whose name contains these words, in any order, ignoring case and accents",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / salonId / description

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

addedOutput schema / properties / clients / description

Added value: +"Clients with the ids needed to look up their bookings, payments and quotes. Email, phone, address, operator notes, service and colour history, organization data and other profile fields are excluded."

First observedSep 25, 2026

TDQS

A4.5/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 real behavioral detail beyond that: the default page size of 20, the hard cap of 100, cross-salon scope, and the exact field set returned. It stops short of describing ordering or how to page beyond the limit, which is the only remaining gap.

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?

Three sentences, each doing distinct work: trigger, return shape, exclusion. The usage trigger is front-loaded and the negative scoping is placed last where it reads as a guardrail. No filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description needn't explain return formatting, and it still summarizes the fields. Annotations cover safety, the schema covers all three parameters, and the description covers trigger, scope and exclusions — nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so limit, search and salonId are already fully documented, including the default, maximum and the 24-hex id pattern. The description restates the same facts ('up to 100 clients (20 by default)', 'across all the user's salons or one', 'only those whose name matches') rather than adding new semantics, so the baseline 3 applies.

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 clients') plus the returned fields (id, name, salon, last edit time) and the cap of 100. It also distinguishes itself from the single-client sibling by explicitly excluding email, phone and notes, which are get_client territory.

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 a concrete trigger ('when someone asks who their clients are, or needs a client's id to book them or to look up their appointments, payments or quotes') and an explicit exclusion ('Not for a client's email, phone or notes'), which routes the agent to get_client. Both when-to-use and when-not-to-use are present.

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?