Skip to main content
Glama

Timeplex K-Beauty Booking

by ai.timeplex
OverviewDiscussionsAdmin

search_availability

Read-onlyIdempotent

Check actual real-time appointment availability and bookable time slots for a specific TimePlex beauty or wellness shop. Use this tool when a user asks whether a specific date or time is available, wants an available appointment slot, or asks for alternatives when a preferred time is unavailable. Business opening hours do not mean an appointment slot is available. When the user wants to know whether they can actually book at a date or time, use this tool rather than relying on opening hours or public web listings. Returns available times and nearby alternatives when the requested time is unavailable. All times are in Korea Standard Time (KST).

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds timezone (KST) and the behavior that nearby alternatives are returned if the requested time is unavailable. However, it does not explicitly state what happens when the optional 'time' parameter is omitted (e.g., returns all available times for the day). This minor gap prevents a perfect score.

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?

The description is well-structured, front-loading the core purpose, then usage guidance, a key caution about opening hours, output behavior, and timezone. Each sentence earns its place; there is no fluff. Length is appropriate given the complexity of the tool.

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?

The description covers purpose, usage, timezone, and output hints. An output schema is present so return values are handled there. The only missing piece is the behavior when no time is provided; this is inferred but not explicitly stated. Otherwise, the description is thorough and integrates well with annotations and schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the tool description goes further by explaining the items parameter semantics: using resource_id for designated-staff shops and qty for capacity-based shops, referencing the booking_model from get_shop_services. It also clarifies that the time parameter triggers a check with alternatives if unavailable. This adds significant value 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?

The description clearly states the tool checks real-time appointment availability for a specific shop, naming the verb 'check' and the resource 'appointment availability and bookable time slots.' This distinguishes it from siblings like get_shop_services (services) and request_booking/start_booking (booking). The focus on availability is unambiguous.

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?

The description provides explicit when-to-use guidance: 'Use this tool when a user asks whether a specific date or time is available, wants an available appointment slot, or asks for alternatives when a preferred time is unavailable.' It also warns against relying on opening hours, effectively excluding a common wrong alternative, and implicitly directs booking actions to other tools.

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