Skip to main content
Glama

Timeplex K-Beauty Booking

by ai.timeplex
OverviewDiscussionsAdmin

search_availability

Read-onlyIdempotent

Check real-time appointment availability for one TimePlex shop (slug from search_shops, items from get_shop_services) on a date, optionally at a time. All times are Korea Standard Time (KST). USE THIS TOOL WHEN: the user asks whether an appointment is available, asks for open slots or possible times, asks for shops that are actually available on a date / at a time / for a party size ("10월 1일 강남 헤드스파 예약 가능한 곳", "any head spa open at 5 PM?", "somewhere I can book tomorrow afternoon for two"), asks for alternatives to an unavailable time, or wants to book (check the slot before start_booking). DO NOT USE IT FOR: find / recommend / compare requests. A date or time alone is not availability intent — "recommend a head spa in Gangnam for October 1" stays a search_shops request unless the user asks whether a slot is open. REAL-TIME RULE: only this tool establishes that a slot is open. Never infer availability from bookable=true, business hours, the shop being open, a service or staff member existing, web search, maps, social media, third-party sites or earlier answers. Describe a time as available only when this tool returns it. PARTY SIZE: check the whole party as the items schema describes (qty for capacity shops). Never stitch separate single-person slots into a group booking unless the result shows it. RESULTS: if the requested time is unavailable, say so and offer the returned alternatives. If blocked is 'inquiry_only', the service cannot be booked online — tell the customer to contact the shop. If nothing is open, say no confirmed slot was found; you may check other suitable TimePlex shops. Checking availability does not reserve anything. NEXT: with the open times you may add start_booking links so the customer can book the slot they pick — never call the slot reserved or booked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesYYYY-MM-DD (Asia/Seoul)
slugYesShop slug returned by search_shops.
timeNoOptional requested appointment time (HH:MM). If provided, check whether that exact time is available and return nearby available alternatives if unavailable.
itemsYesBooking items. Follow the booking_model returned by get_shop_services: use resource_id for designated-staff shops and qty for capacity-based shops. designated (hair salons, plus some beauty shops such as body scrub): [{service_id, resource_id}]. capacity (most massage, spa, etc.): [{service_id, qty}] where qty is the number of guests (party size).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
modeNoSlot mode the shop operates in
noteNo
slotsYes
blockedNoPresent when online booking is blocked (e.g. 'inquiry_only')
timezoneNo
next_stepNo
alternativesNoNearby bookable times when the requested time is not available
requested_timeNoVerdict for the exact time asked, when time was given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / description
      Previous value: -"Booking items. Follow the booking_model returned by get_shop_services: use resource_id for designated-staff shops and qty for capacity-based shops. designated (hair salons, plus some beauty shops such as body scrub): [{service_id, resource_id}]. capacity (most massage, spa, etc.): [{service_id, qty}] where qty is the number of people."New value: +"Booking items. Follow the booking_model returned by get_shop_services: use resource_id for designated-staff shops and qty for capacity-based shops. designated (hair salons, plus some beauty shops such as body scrub): [{service_id, resource_id}]. capacity (most massage, spa, etc.): [{service_id, qty}] where qty is the number of guests (party size)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / items / description
      Previous value: -"Booking items. Hair: [{service_id, resource_id}]. Massage: [{service_id, qty}] (qty = number of people)."New value: +"Booking items. Follow the booking_model returned by get_shop_services: use resource_id for designated-staff shops and qty for capacity-based shops. designated (hair salons, plus some beauty shops such as body scrub): [{service_id, resource_id}]. capacity (most massage, spa, etc.): [{service_id, qty}] where qty is the number of people."
    • addedInput schema / properties / slug / description
      Added value: +"Shop slug returned by search_shops."
    • changedInput schema / properties / time / description
      Previous value: -"HH:MM (optional) — judge whether this exact time is bookable"New value: +"Optional requested appointment time (HH:MM). If provided, check whether that exact time is available and return nearby available alternatives if unavailable."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "alternatives": {
+      "description": "Nearby bookable times when the requested time is not available",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "blocked": {
+      "description": "Present when online booking is blocked (e.g. 'inquiry_only')",
+      "type": "string"
+    },
+    "date": {
+      "type": "string"
+    },
+    "mode": {
+      "description": "Slot mode the shop operates in",
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "requested_time": {
+      "description": "Verdict for the exact time asked, when time was given.",
+      "properties": {
+        "available": {
+          "type": "boolean"
+        },
+        "time": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "slots": {
+      "items": {
+        "properties": {
+          "available": {
+            "type": "boolean"
+          },
+          "time": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timezone": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "slots"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the real-time rule (only this tool proves a slot is open), the fact that checking reserves nothing, and the inquiry_only blocked behavior. That is exactly the value-add expected when annotations carry the safety profile.

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?

Long but deliberately front-loaded and chunked under labeled headers (USE THIS TOOL WHEN, DO NOT USE IT FOR, REAL-TIME RULE, PARTY SIZE, RESULTS, NEXT), so it is scannable. It is still verbose and repeats the availability rule more than once, keeping it short of a 5.

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 and annotations covering safety, the description supplies the remaining operational context an agent needs: interpretation of blocked/inquiry_only, what to say when nothing is open, and the follow-up to start_booking without implying a reservation.

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. The description reinforces sourcing (slug from search_shops, items from get_shop_services) and the KST convention, but the designated-vs-capacity booking_model guidance it gives is already spelled out in the items schema, so it adds little beyond the structured fields.

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 precise verb and resource (check real-time appointment availability for one TimePlex shop on a date, optionally a time) and immediately scopes it by naming the source of slug and items, which separates it from search_shops and get_shop_services.

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?

Explicit USE THIS TOOL WHEN / DO NOT USE IT FOR blocks with concrete multilingual trigger phrases and a clear exclusion ('a date or time alone is not availability intent — stays a search_shops request'). Alternatives are named rather than implied.

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

All Timeplex K-Beauty Booking toolsInspect
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