Skip to main content
Glama

Timeplex K-Beauty Booking

search_shops

Read-onlyIdempotent

Search TimePlex for massage, headspa, hair salon, spa, Korean body scrub, and makeup shops in Seoul and Korea — non-medical beauty and wellness services for travelers. Use this tool as the first step when a user wants to find, compare, or book a service but has not selected a specific TimePlex shop yet, including requests asking what is available today, tomorrow, on a specific date or time, within a time range, or for multiple guests. Examples include "massage in Seoul available today", "lymphatic massage near Hongdae", "headspa in Gangnam tomorrow for 2 people", "scalp treatment in Myeongdong", "English-speaking hair salon in Seoul", "hair color in Myeongdong", "spa available tomorrow", "Korean body scrub in Seoul", and "Korean makeup in Seoul". Relevant user terms include massage, lymphatic massage, headspa, head spa, scalp treatment, scalp care, hair salon, haircut, hair color, perm, spa, Korean body scrub, seshin, akasuri, makeup, makeup salon, and semi-permanent makeup (PMU, microblading, brow tattoo, lip blush, eyeliner). Pass the user's request as query, in any language: the service, area, date, time, party size and language needs are extracted from it (see interpreted in the response). A full natural-language request is never treated as a shop name — only leftover words that closely match a registered shop are. Every TimePlex shop supports foreign-language customers through TimePlex multilingual chat, so requests for English-speaking or foreigner-friendly shops are a good fit for this tool. Shops are also matched by their menu (e.g. a hair salon with a scalp-care menu is returned for headspa); matched_services lists those menu items. If no shop is in the requested area, the search widens to the surrounding city and relaxed says so. This tool is for non-medical services only — do not use it for dermatology, clinics, plastic surgery, injections, lasers, or other medical procedures. This tool finds matching TimePlex shops; it does not by itself confirm an appointment slot. For bookable=true shops, continue with get_shop_services and search_availability to check actual booking availability. Do not treat business opening hours as proof that an appointment is available. Results indicate whether each shop is bookable through TimePlex: bookable=true means real-time availability can be checked and the customer can proceed to booking through this MCP; bookable=false means it needs request_booking (TimePlex concierge arranges it manually). Shops fall into two categories: hair (hair salons) and beauty (everything else). Each shop result carries its category. If the user named a specific shop that is not registered, the response sets shop_name_not_found — tell the user that shop is not on TimePlex and offer the registered shops in the result as alternatives. If unsupported_service is set, that kind of service is not on TimePlex yet — say so instead of offering other shops. Each result carries the shop address, so you can answer area questions ("shops in Seoul") without extra calls. Always reply to the user in the language they used, and start the reply with the response's reply_header line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text user request or a specific shop name (optional), in any language. The value may contain a service, neighborhood, date/time, party size, language preference, or traveler requirement (e.g. "foreigner-friendly head spa in Gangnam tomorrow for 2 people"). Recognized service and location terms are extracted before shop-name matching; the value is treated as a shop name only when the remaining words closely match a registered shop.
locationNoArea (optional; overrides an area found in query), in English, Korean, Japanese, Chinese or Russian — "Seoul", "Gangnam", "Myeongdong", "Hongdae", "Seongsu", "Busan", "강남", "明洞", "Сеул"… If no shop is in that area, the search widens to the surrounding city (relaxed). Newly joined shops with no address yet are appended with area_match=false.
service_typeNoService (optional; overrides a service found in query). Available on TimePlex now: massage, head spa / scalp treatment, hair salon, spa, Korean body scrub (seshin, akasuri), makeup, semi-permanent makeup (PMU, microblading, brow tattoo) — in English, Korean, Japanese, Chinese or Russian (マッサージ, ヘッドスパ, アカスリ, 按摩, 搓澡, массаж, сесин…). Other services (nail, lash, facial, personal color) are recognized but may return unsupported_service. Leave empty to search all.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoFollow-up guidance for the agent
countYes
shopsYesMatching shops.
relaxedNoSet when no shop was in the requested area and the search widened: {area:{from,to}}.
categoriesNo
interpretedNoHow the request was read: service (massage|headspa|hair|spa|scrub|makeup|…), area, foreigner_friendly, date (YYYY-MM-DD, KST), time, time_range, time_of_day, party_size, gender, attributes, name_query (leftover words treated as a shop name), ignored_terms. Use date/time/party_size for search_availability (party_size → qty).
reply_headerNo
filter_appliedNoHow the inputs were interpreted (category/service_type/location/query)
reply_header_usageNo
shop_name_not_foundNoSet when the user named a specific shop that is not registered on Timeplex. Tell the user that shop is not on Timeplex — do not treat it as a category with zero results, and do not submit it with request_booking.
unsupported_serviceNoA recognized service that is not on TimePlex yet (e.g. nail, lash, facial, personal_color).
available_service_typesNobusiness_type values currently registered

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Area (optional; overrides an area found in query), in English, Korean, Japanese or Chinese — \"Seoul\", \"Gangnam\", \"Myeongdong\", \"Hongdae\", \"Seongsu\", \"Busan\", \"강남\", \"明洞\"… If no shop is in that area, the search widens to the surrounding city (relaxed). Newly joined shops with no address yet are appended with area_match=false."New value: +"Area (optional; overrides an area found in query), in English, Korean, Japanese, Chinese or Russian — \"Seoul\", \"Gangnam\", \"Myeongdong\", \"Hongdae\", \"Seongsu\", \"Busan\", \"강남\", \"明洞\", \"Сеул\"… If no shop is in that area, the search widens to the surrounding city (relaxed). Newly joined shops with no address yet are appended with area_match=false."
    • changedInput schema / properties / service_type / description
      Previous value: -"Service (optional; overrides a service found in query). Available on TimePlex now: massage, head spa / scalp treatment, hair salon, spa, Korean body scrub (seshin, akasuri), makeup, semi-permanent makeup (PMU, microblading, brow tattoo) — in English, Korean, Japanese or Chinese (マッサージ, ヘッドスパ, アカスリ, 按摩, 搓澡…). Other services (nail, lash, facial, personal color) are recognized but may return unsupported_service. Leave empty to search all."New value: +"Service (optional; overrides a service found in query). Available on TimePlex now: massage, head spa / scalp treatment, hair salon, spa, Korean body scrub (seshin, akasuri), makeup, semi-permanent makeup (PMU, microblading, brow tattoo) — in English, Korean, Japanese, Chinese or Russian (マッサージ, ヘッドスパ, アカスリ, 按摩, 搓澡, массаж, сесин…). Other services (nail, lash, facial, personal color) are recognized but may return unsupported_service. Leave empty to search all."
  2. Changed7 schema fields changed
    • changedInput schema / properties / location / description
      Previous value: -"Area filter (optional), in English or Korean — \"Seoul\", \"Gangnam\", \"Hongdae\", \"Busan\", \"Jeju\", \"강남\", \"홍대\"… Matched against the shop address. Shops with no address registered are excluded when this is set."New value: +"Area (optional; overrides an area found in query), in English, Korean, Japanese or Chinese — \"Seoul\", \"Gangnam\", \"Myeongdong\", \"Hongdae\", \"Seongsu\", \"Busan\", \"강남\", \"明洞\"… If no shop is in that area, the search widens to the surrounding city (relaxed). Newly joined shops with no address yet are appended with area_match=false."
    • changedInput schema / properties / query / description
      Previous value: -"Shop name, service, or natural-language search term (optional). If no shop name matches, it is also interpreted as a service/category search."New value: +"Free-text user request or a specific shop name (optional), in any language. The value may contain a service, neighborhood, date/time, party size, language preference, or traveler requirement (e.g. \"foreigner-friendly head spa in Gangnam tomorrow for 2 people\"). Recognized service and location terms are extracted before shop-name matching; the value is treated as a shop name only when the remaining words closely match a registered shop."
    • changedInput schema / properties / service_type / description
      Previous value: -"Shop category (optional). Accepts broad categories (\"hair\", \"beauty\") and specific ones (\"massage\", \"spa\", \"head spa\", \"nail\", \"skincare\", \"facial\", \"esthetic\", \"waxing\", \"scrub\"), in English, Korean, Japanese or Chinese (アカスリ, ヘッドスパ, マッサージ, 搓澡, 头皮护理, 按摩…). Leave empty to search all categories."New value: +"Service (optional; overrides a service found in query). Available on TimePlex now: massage, head spa / scalp treatment, hair salon, spa, Korean body scrub (seshin, akasuri), makeup, semi-permanent makeup (PMU, microblading, brow tattoo) — in English, Korean, Japanese or Chinese (マッサージ, ヘッドスパ, アカスリ, 按摩, 搓澡…). Other services (nail, lash, facial, personal color) are recognized but may return unsupported_service. Leave empty to search all."
    • addedOutput schema / properties / interpreted
      Added value: +{
      +  "description": "How the request was read: service (massage|headspa|hair|spa|scrub|makeup|…), area, foreigner_friendly, date (YYYY-MM-DD, KST), time, time_range, time_of_day, party_size, gender, attributes, name_query (leftover words treated as a shop name), ignored_terms. Use date/time/party_size for search_availability (party_size → qty).",
      +  "type": "object"
      +}
    • addedOutput schema / properties / relaxed
      Added value: +{
      +  "description": "Set when no shop was in the requested area and the search widened: {area:{from,to}}.",
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / shops / items / properties / matched_services
      Added value: +{
      +  "description": "Present when the shop matched through its menu: the menu items (original names) that matched the request. Pick the service from these in get_shop_services.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / unsupported_service
      Added value: +{
      +  "description": "A recognized service that is not on TimePlex yet (e.g. nail, lash, facial, personal_color).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / shops / items / properties / business_type / description
      Added value: +"Filter code. Use business_type_label when naming the shop to the user."
    • addedOutput schema / properties / shops / items / properties / business_type_label
      Added value: +{
      +  "description": "Display label the shop selected (spa = 스파·헤드스파 / spa & head spa). null when unset.",
      +  "properties": {
      +    "en": {
      +      "type": "string"
      +    },
      +    "ko": {
      +      "type": "string"
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / service_type / description
      Previous value: -"Shop category (optional). Accepts broad categories (\"hair\", \"beauty\") and specific ones (\"massage\", \"spa\", \"head spa\", \"nail\", \"skincare\", \"facial\", \"esthetic\", \"waxing\", \"scrub\"), in English or Korean. Leave empty to search all categories."New value: +"Shop category (optional). Accepts broad categories (\"hair\", \"beauty\") and specific ones (\"massage\", \"spa\", \"head spa\", \"nail\", \"skincare\", \"facial\", \"esthetic\", \"waxing\", \"scrub\"), in English, Korean, Japanese or Chinese (アカスリ, ヘッドスパ, マッサージ, 搓澡, 头皮护理, 按摩…). Leave empty to search all categories."
  5. Changed1 schema field changed
    • addedOutput schema / properties / shop_name_not_found
      Added value: +{
      +  "description": "Set when the user named a specific shop that is not registered on Timeplex. Tell the user that shop is not on Timeplex — do not treat it as a category with zero results, and do not submit it with request_booking.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  6. Changed4 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Shop name, partial match (optional). If no name matches, it is also interpreted as a shop category."New value: +"Shop name, service, or natural-language search term (optional). If no shop name matches, it is also interpreted as a service/category search."
    • changedInput schema / properties / service_type / description
      Previous value: -"Shop category (optional). Accepts broad categories (\"hair\", \"beauty\") and specific ones (\"massage\", \"spa\", \"head spa\", \"nail\", \"skin care\", \"esthetic\", \"waxing\", \"scrub\"), in English or Korean. Leave empty to search all categories."New value: +"Shop category (optional). Accepts broad categories (\"hair\", \"beauty\") and specific ones (\"massage\", \"spa\", \"head spa\", \"nail\", \"skincare\", \"facial\", \"esthetic\", \"waxing\", \"scrub\"), in English or Korean. Leave empty to search all categories."
    • addedOutput schema / properties / shops / items / properties / address / description
      Added value: +"null = newly joined shop that has not registered an address yet"
    • addedOutput schema / properties / shops / items / properties / area_match
      Added value: +{
      +  "description": "Present only when a location filter was applied: true = address matched the area; false = no address registered yet (newly onboarding) — confirm the area with the shop",
      +  "type": "boolean"
      +}
  7. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "available_service_types": {
      +      "description": "business_type values currently registered",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "categories": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "count": {
      +      "type": "integer"
      +    },
      +    "filter_applied": {
      +      "description": "How the inputs were interpreted (category/service_type/location/query)",
      +      "type": "object"
      +    },
      +    "note": {
      +      "description": "Follow-up guidance for the agent",
      +      "type": "string"
      +    },
      +    "reply_header": {
      +      "type": "string"
      +    },
      +    "reply_header_usage": {
      +      "type": "string"
      +    },
      +    "shops": {
      +      "description": "Matching shops.",
      +      "items": {
      +        "properties": {
      +          "address": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "bookable": {
      +            "description": "true = bookable via this MCP; false = use request_booking",
      +            "type": "boolean"
      +          },
      +          "business_type": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "category": {
      +            "enum": [
      +              "hair",
      +              "beauty"
      +            ],
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "description": "Shop id for the other tools",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "shops",
      +    "count"
      +  ],
      +  "type": "object"
      +}
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavioral context beyond them: bookable=true vs false routing to request_booking, shop_name_not_found and unsupported_service signals, relaxed widening, and the reply_header convention. This is rich disclosure of edge-case behavior.

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?

It is front-loaded with purpose and scope, and each block carries operational value (routing, error flags, next steps). However, the enumeration of example phrases and synonym lists is long enough that the core instruction is somewhat buried; minor trimming would sharpen it.

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?

For a search tool over a domain with several distinct response flags, the description covers service scope, language handling, widening behavior, error signals, and next-step routing. With an output schema present, no return-value explanation is needed, so the definition is complete.

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 schema already documents all three parameters and the baseline of 3 applies. The description still adds meaning beyond it: that query is parsed for service/area/date/party-size/language, that location and service_type override values found in query, and that a natural-language request is never treated as a shop name.

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 opens with a specific verb+resource ('Search TimePlex for massage, headspa, hair salon, spa, Korean body scrub, and makeup shops in Seoul and Korea') and frames the domain precisely. It distinguishes itself from siblings by declaring it is 'the first step' in discovery versus booking, making the boundary with get_shop_services/search_availability explicit.

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 states exactly when to use it (user wants to find/compare/book but hasn't picked a shop, including date/time/party-size variants) and names the follow-on tools ('continue with get_shop_services and search_availability'). Negative guidance is equally explicit: no medical/dermatology/plastic surgery, and it warns not to treat opening hours as booking proof.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources