Timeplex K-Beauty Booking

Get Shop Services

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

Name	Required	Description	Default
`lang`	No	Customer language (optional): ko\|en\|ja\|zh\|th. Defaults to the original text (ko).
`slug`	Yes	Shop slug returned by search_shops

Output Schema

Name	Required	Description
`lang`	No
`note`	No
`shop`	Yes
`services`	Yes
`resources`	No	Staff to designate (designated-staff shops) or seats (capacity-based shops).
`booking_model`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 1, 2026

addedOutput schema / properties / booking_model / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / booking_model / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedOutput schema / properties / services / items / properties / duration_min / anyOf
```
Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / properties / services / items / properties / duration_min / type
```
Removed value: -[
-  "integer",
-  "null"
-]
```

addedOutput schema / properties / services / items / properties / price / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / services / items / properties / price / type
```
Removed value: -[
-  "number",
-  "string",
-  "null"
-]
```

addedOutput schema / properties / shop / properties / business_hours / anyOf

Added value: +[
+  {
+    "items": {
+      "properties": {
+        "close": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "closed": {
+          "description": "true = closed that weekday",
+          "type": "boolean"
+        },
+        "open": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / shop / properties / business_hours / items

Removed value: -{
-  "properties": {
-    "close": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "closed": {
-      "description": "true = closed that weekday",
-      "type": "boolean"
-    },
-    "open": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / shop / properties / business_hours / type
```
Removed value: -[
-  "array",
-  "null"
-]
```

addedOutput schema / properties / shop / properties / business_type / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / shop / properties / business_type / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed4 schema fields changedAug 24, 2026

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"
+]

Changed2 schema fields changedAug 23, 2026

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)."

Changed1 schema field changedAug 22, 2026

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"
+}

First observedAug 18, 2026

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, closed-world, so the bar is lower; the description still adds non-obvious traits: unbookable services are pre-filtered out of the result, open hours and existing staff do not imply a free slot, no substitution when a service is missing, and lang triggers translated content. It also explains why the returned service ids and booking_model matter downstream.

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?

Front-loaded with the core purpose, then clearly labeled WHEN / DO NOT USE / DATA / NEXT blocks, so an agent can scan to what it needs. The SERVICE DATA and RESOURCES & HOURS sections are somewhat verbose and repeat the same no-invention constraint in several forms, costing a little length.

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?

Output schema exists, so return values need no explanation; the description instead covers what an agent must not infer from the data and where to route next, which is exactly the gap. For a two-parameter read tool with full annotation coverage, nothing needed to call or interpret it 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 description coverage is 100%, so both slug and lang are already documented in the schema, and the description's 'slug from search_shops' and 'Pass lang to receive the content translated' largely restate them. Baseline 3 applies since the schema does the heavy lifting.

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?

Names a specific verb and resource ('Get the services, prices, durations, weekly business hours and bookable staff or seats of one specific TimePlex shop') and pins the input to a slug from search_shops. An agent can distinguish it from search_shops, search_availability, and start_booking without opening any schema.

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 section covers menu/prices/durations/staff queries and the prerequisite role before search_availability and start_booking, while DO NOT USE IT FOR names each sibling and the condition that selects it. The NEXT paragraph further disambiguates the common failure mode of over-checking availability when the user only asked about the menu.

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 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?