Skip to main content
Glama

Timeplex K-Beauty Booking

by ai.timeplex
OverviewDiscussionsAdmin

get_shop_services

Read-onlyIdempotent

Get the services, prices, durations, weekly business hours and bookable staff or seats of one specific TimePlex shop (slug from search_shops). USE THIS TOOL WHEN: a shop has been identified and the user asks what it offers, prices, durations or staff; to match requirements (a 60-minute head spa, a budget, two guests at once); or before search_availability / start_booking, which need the service ids and booking_model returned here. DO NOT USE IT FOR: general discovery or recommendations (search_shops), real-time availability (search_availability), or building a booking link (start_booking). SERVICE DATA: describe only the services returned here — never invent names, prices, durations, staff or options, and never assume a service exists because similar shops offer it. Services that cannot be booked online are already excluded. If the requested service is not in the list, say so; do not silently substitute another. Never present medical procedures as TimePlex services. RESOURCES & HOURS: a staff member or seat existing, or the shop being open, does NOT mean it is free at the requested time — only search_availability confirms a slot. NEXT: if the user asked for availability or to book, continue to search_availability with the returned service ids and booking_model instead of stopping at the menu or business hours. If they only asked about the menu, prices or durations, answer from this result and do not check availability or build a booking link unless they ask. A date or time mentioned earlier does not by itself require a slot check. Pass lang to receive the content translated into the customer's language.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoCustomer language (optional): ko|en|ja|zh|th. Defaults to the original text (ko).
slugYesShop slug returned by search_shops

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo
noteNo
shopYes
servicesYes
resourcesNoStaff to designate (designated-staff shops) or seats (capacity-based shops).
booking_modelNoHow this shop books: 'designated' — pass items as [{service_id, resource_id}]; 'capacity' — pass items as [{service_id, qty}]. Use this for search_availability and start_booking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / resources / items / properties / service_ids
      Added value: +{
+  "description": "Services this staff/seat handles. Empty = handles every service. Pass this resource only for a service in this list.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / shop / properties / business_hours / description
      Added value: +"Weekly hours, index 0 = Sunday: [{open:\"10:30\", close:\"21:00\", closed:false} × 7]"
    • addedOutput schema / properties / shop / properties / business_hours / items
      Added value: +{
+  "properties": {
+    "close": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "closed": {
+      "description": "true = closed that weekday",
+      "type": "boolean"
+    },
+    "open": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • changedOutput schema / properties / shop / properties / business_hours / type
      Previous value: -[
-  "object",
-  "null"
-]New value: +[
+  "array",
+  "null"
+]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / booking_model
      Added value: +{
+  "description": "How this shop books: 'designated' — pass items as [{service_id, resource_id}]; 'capacity' — pass items as [{service_id, qty}]. Use this for search_availability and start_booking.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / resources / description
      Previous value: -"Staff (hair) or seats (massage)."New value: +"Staff to designate (designated-staff shops) or seats (capacity-based shops)."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "lang": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "resources": {
+      "description": "Staff (hair) or seats (massage).",
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "services": {
+      "items": {
+        "properties": {
+          "currency": {
+            "type": "string"
+          },
+          "duration_min": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Pass as items[].service_id to search_availability / start_booking",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price": {
+            "type": [
+              "number",
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "shop": {
+      "properties": {
+        "address": {
+          "type": "string"
+        },
+        "business_hours": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "business_type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "map_url": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "shop",
+    "services"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.8/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 layers on real behavioral context: services not bookable online are pre-excluded, a staff member existing does not mean availability, and medical procedures must never be presented as TimePlex services. This is disclosure beyond the annotation 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?

Lengthy, but organized into labeled blocks (USE WHEN / DO NOT USE / SERVICE DATA / RESOURCES & HOURS / NEXT) with the core purpose front-loaded. A few guardrail sentences are verbose, but each carries a distinct constraint an agent could otherwise get wrong.

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?

An output schema exists so return shape need not be spelled out, yet the description still tells the agent what the result contains and how to use it downstream (service ids and booking_model for search_availability). Nothing needed to call or sequence this tool correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds genuine meaning for lang ('Pass lang to receive the content translated into the customer's language'), clarifying its effect rather than just restating the enum values.

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 opening sentence states a precise verb and resource and enumerates the exact payload: services, prices, durations, weekly business hours, bookable staff/seats, scoped to one shop identified by slug. It is clearly distinguishable from search_shops (discovery) and search_availability (slots).

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 naming all three relevant siblings, plus a NEXT section that states whether to continue to search_availability or stop. It even handles the edge case that a previously mentioned date does not by itself require a slot check.

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