NailMe – Book nail studios

Find courses

find_courses

Read-only

Upcoming courses and training sessions with limited seats near a location or in a city, in-person ones nearest first, then by date. Online sessions are not limited by location. Only sessions still open for booking: canceled and past sessions are left out, a full session has seats.free 0 and waitlist true. Each session lists its dates, price or deposit, certificate and free seats. Nothing is booked: give the user the confirm_url. Times are in the studio time zone.

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": "find_courses"
  }
}

Input Schema

Name	Required	Description
`city`	No	City name, used when no coordinates are known
`level`	No	beginner, advanced or master
`limit`	No	Max courses, default 10, at most 30
`query`	No	Words the course title or description must contain, e.g. "gel"
`format`	No
`to_date`	No	YYYY-MM-DD: only courses that start on or before this day
`latitude`	No
`from_date`	No	YYYY-MM-DD: only courses that last until this day or later
`longitude`	No
`radius_km`	No	Search radius for in-person courses, default 25

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Goes well beyond the read-only/non-destructive annotations: it discloses result ordering, exclusion of canceled and past sessions, how a full session is encoded (seats.free 0, waitlist true), the per-session fields returned, that nothing is booked and the confirm_url should be surfaced, and that times are in studio time zone. Pagination behavior beyond the limit parameter is the main omission.

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?

The purpose is front-loaded in the first sentence and subsequent sentences each carry real information (ordering, filtering, full-session encoding, booking hand-off, time zone). Density is high with little filler, though a couple of clauses could be merged for tighter reading.

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 10-parameter, no-output-schema search tool, the description does the important work of describing the returned record and its ordering/filtering semantics. Remaining gaps (pagination, behavior when both city and coordinates are supplied) are minor and partly covered by 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 coverage is 70%, so most parameters are documented structurally. The description adds only modest meaning: that location (coordinates) and city are alternative ways to search and that online sessions ignore location, which clarifies how radius_km and coordinates interact. It says nothing extra about query, level, or date params.

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?

States a specific verb and resource with scope: upcoming courses and training sessions with limited seats near a location or in a city, including sort order (nearest first, then date). It does not explicitly name a sibling, but the closing line 'Nothing is booked: give the user the confirm_url' implies the hand-off to prepare_booking.

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

Usage Guidelines3/5

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

Usage is implied by the framing (find sessions near a location or in a city; online sessions are not location-bound), and result filtering (no canceled/past sessions) is spelled out. However, there is no explicit 'use this when… / use search_studios or find_free_slots instead' guidance, leaving the agent to infer the choice among siblings.

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

All NailMe – Book nail studios 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?