Skip to main content
Glama

Timeplex K-Beauty Booking

Search Shops

search_shops
Read-onlyIdempotent

Search TimePlex for massage, headspa, hair salon, spa, Korean body scrub, makeup and semi-permanent makeup shops in Seoul and Korea — non-medical beauty and wellness services for travelers. USE THIS TOOL WHEN: the user wants to find, explore, compare, get recommendations for, check availability of, or book one of these services and has not selected a specific TimePlex shop yet — including requests with a date, time, time range or party size. Relevant terms: 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, semi-permanent makeup (PMU, microblading, brow tattoo, lip blush, eyeliner). Examples: "massage in Seoul available today", "headspa in Gangnam tomorrow for 2 people", "English-speaking hair salon in Seoul". WEB SEARCH: for these services use this tool instead of web search. Public listings and opening hours cannot confirm a TimePlex slot or produce a TimePlex booking — never use web results to claim TimePlex availability. INTENT — decide from what the user wants to do, not from whether a date, time, party size or the word "reservation" appears:

  • FIND / RECOMMEND / COMPARE ("find a head spa in Gangnam", "recommend a head spa for my October 1 trip", "10/1 강남 헤드스파 추천해줘"): show the matching shops. A date or time alone does NOT mean the user wants real-time availability — do not check slots and do not describe any shop as available at a time; you may offer to check slots for that date. Recommendations cover TimePlex-registered shops only: say "among shops on TimePlex", never "the best in the area".

  • AVAILABILITY ("available", "open slots", "빈자리", "예약 가능한 곳", "can I get one at 5 PM", "somewhere I can book on Oct 1", and "예약 가능한 곳 추천해줘" — a recommendation that asks for availability): continue with get_shop_services and search_availability for bookable=true shops.

  • BOOK ("book", "reserve", "예약해줘", "I want to book … for 2 people at 5pm"): continue with get_shop_services, search_availability and start_booking. If the intent is unclear, show the shops and ask one short question instead of guessing. INPUT: pass the user's full request as query, in any language — service, area, date, time, party size and language needs are extracted from it (see interpreted). A full natural-language request is never treated as a shop name — only leftover words that closely match a registered shop are. BOOKABLE: bookable=true means the shop can be booked through TimePlex — a capability, not a free slot. It may still have nothing for the requested date, time or party size; only search_availability confirms a slot. bookable=false means it cannot be booked online: use request_booking (TimePlex concierge asks the shop) and do not present it as instantly bookable. Business hours are never availability. SERVICE SCOPE: the response is the authority on what TimePlex offers (available_service_types). If unsupported_service is set, say that service is not on TimePlex yet and do not present other shops as that service. Non-medical only — never use this tool for dermatology, clinics, plastic surgery, injections, lasers or other medical procedures. SHOP NAMES: if shop_name_not_found is set, say plainly that the named shop is not on TimePlex, then offer the registered shops in the result as alternatives; do not call request_booking for that name. RESULTS: every TimePlex shop supports foreign-language customers through TimePlex multilingual chat, so "English-speaking" / "foreigner-friendly" requests fit this tool. Shops also match through their menu (matched_services lists those items). If no shop is in the requested area the search widens and relaxed says so. Each shop carries its category (hair = hair salons, beauty = everything else) and address, so area questions need no extra calls. note is guidance for you — follow it, do not quote it. State only what the response returns. Always reply in the user's language, and start the reply with the response's reply_header line.

Input 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

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. Changed13 schema fields changed
    • addedOutput schema / properties / relaxed / anyOf
      Added value: +[
      +  {
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / relaxed / type
      Removed value: -[
      -  "object",
      -  "null"
      -]
    • addedOutput schema / properties / shop_name_not_found / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / shop_name_not_found / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / shops / items / properties / address / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / shops / items / properties / address / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / shops / items / properties / business_type / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / shops / items / properties / business_type / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
    • addedOutput schema / properties / shops / items / properties / business_type_label / anyOf
      Added value: +[
      +  {
      +    "properties": {
      +      "en": {
      +        "type": "string"
      +      },
      +      "ko": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / shops / items / properties / business_type_label / properties
      Removed value: -{
      -  "en": {
      -    "type": "string"
      -  },
      -  "ko": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / shops / items / properties / business_type_label / type
      Removed value: -[
      -  "object",
      -  "null"
      -]
    • addedOutput schema / properties / unsupported_service / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / unsupported_service / type
      Removed value: -[
      -  "string",
      -  "null"
      -]
  2. 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."
  3. 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"
      +  ]
      +}
  4. 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"
      +  ]
      +}
  5. 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."
  6. 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"
      +  ]
      +}
  7. 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"
      +}
  8. 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"
      +}
  9. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses non-obvious semantics that annotations cannot carry: bookable=true is a capability rather than a free slot, bookable=false routes to request_booking, business hours are never availability, searches widen when the area has no shops (relaxed), and unsupported_service / shop_name_not_found are named response states the agent must handle. It also tells the agent not to quote the note field and to state only what the response returns, which is genuine behavioral guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and organized under CAPS headers, but the block is very long for a search tool and repeats itself — the availability-vs-recommendation distinction is restated in the INTENT section, again under BOOKABLE, and again under RESULTS, and the service list appears in both the opening line and SERVICE SCOPE. It remains readable, yet a tighter version could carry the same routing rules in noticeably fewer words.

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 zero-required-parameter router tool sitting alongside booking siblings, the definition covers what an agent needs: trigger conditions, intent branching, input assembly, response-state handling (relaxed, unsupported_service, shop_name_not_found, matched_services, area_match), and a reply-language instruction. Return-value explanation is partly redundant with the output schema, but nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: the query should carry the user's full natural-language request in any language, and it explains that such a request is never mistaken for a shop name unless leftover words closely match a registered shop. It also clarifies the precedence relationship (explicit location/service_type override values found in query), which is the key semantic an agent needs to choose between passing everything in query versus the discrete fields.

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 names a specific verb (search) and a concrete resource set (massage, headspa, hair salon, spa, body scrub, makeup shops) with geography (Seoul/Korea) and a scope boundary (non-medical beauty and wellness). Sibling tools are explicitly referenced (get_shop_services, search_availability, start_booking, request_booking), so the agent can distinguish discovery from booking without opening a 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?

A dedicated 'USE THIS TOOL WHEN' block gives the positive trigger, and the INTENT section enumerates three intents (FIND/RECOMMEND/COMPARE, AVAILABILITY, BOOK) each mapped to the next sibling tool to call, plus explicit exclusions (medical/dermatology/clinics) and an instruction to show shops and ask one question when intent is unclear. It even pre-empts web search for these services, which is a real alternative the agent might otherwise pick.

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