Skip to main content
Glama

Timeplex K-Beauty Booking

by ai.timeplex
OverviewDiscussionsAdmin

get_shop_services

Read-onlyIdempotent

Get the available services, prices, durations, and bookable staff or resources for a specific TimePlex beauty or wellness shop. Use this after search_shops when service details, prices, durations, staff, resources, or bookable items are needed before checking appointment availability. If the user has asked to book or check availability, use the returned service/item IDs and booking_model to continue to search_availability rather than stopping after showing the menu or business hours. 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.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description does not need to repeat those. It adds useful behavioral context beyond annotations: the response is localization-aware via lang, and the returned booking_model/service/item IDs are meant to be consumed downstream by search_availability.

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 description is front-loaded with the core purpose and every sentence carries useful routing information. It is slightly verbose with repeated detail lists, but remains readable and efficient enough for an agent to parse quickly.

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?

Given the output schema exists, the annotations are rich, and the workflow position is clearly defined, the description covers what an agent needs: when to call it, what it returns conceptually, and how to continue to search_availability. No critical usage gap remains.

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 schema already documents both parameters. The description adds marginal context by noting slug comes from search_shops and that lang controls translation, but it does not substantially expand on the structured parameter definitions.

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 states a specific action ('Get the available services, prices, durations, and bookable staff or resources') and a clear resource ('a specific TimePlex beauty or wellness shop'). It is immediately distinguishable from siblings like search_shops and search_availability by naming exactly what data it returns.

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?

It explicitly tells the agent when to use the tool: 'after search_shops' and 'when service details, prices, durations, staff, resources, or bookable items are needed before checking appointment availability.' It also names the alternative path, directing continued workflow to search_availability and warning against stopping after showing the menu or business hours.

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