F
license-
qualityB
maintenance22,000+ public facility data for foreign tourists in Seoul — restrooms, pharmacies, WiFi, AEDs, tourist info centers, and subway timetables. Bilingual (Korean/English).
Seoul Tourism (Visit Seoul)
Server Details
Official Seoul tourism data in 7 languages, in cooperation with the Seoul Tourism Organization.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.2/5 across 3 of 3 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool serves a unique, clearly distinct purpose: search_contents for searching, get_content_detail for retrieving detailed info by ID, and get_sync_status for checking data freshness. No overlap in functionality.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern with snake_case: search_contents, get_content_detail, get_sync_status. The pattern is predictable and intuitive.
Tool Count4/5
With 3 tools, the set is slightly small but appropriate for a focused tourism data query service. Each tool is essential and covers core operations without unnecessary bloat.
Completeness4/5
The tools cover the primary use cases: searching by various filters, getting detailed content, and checking data sync status. Minor gaps exist (e.g., no direct listing of categories or recommendations), but the core information retrieval workflow is complete.
Available Tools
3 toolsget_content_detailARead-onlyInspect
검색 결과의 콘텐츠 ID로 상세 정보(운영시간·주소·연락처·이미지·일정 등)를 조회한다. language로 번역 버전을 가져온다. 요청 언어판이 없으면 한국어로 대체한다.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | 콘텐츠 ID (search_contents 결과의 id) | |
| language | No | 언어. ko(기본)/en/ja/zh-CN/zh-TW/ru/ms |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the tool is safe. The description adds transparency about behavior: it retrieves details and provides language fallback to Korean if the requested version is unavailable. This extra context justifies a score of 4.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences that are front-loaded with the primary action, then secondary detail. No redundant information; every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description lists the types of information returned (hours, address, etc.) and handles language behavior. It provides sufficient context for an agent to understand what to expect, though a sample response could further improve completeness.
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% with descriptions for both parameters. The description adds value by clarifying that 'id' comes from search_contents results and explaining the language fallback logic, which goes beyond what the schema provides.
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 clearly specifies the action: retrieve detailed information (business hours, address, contact, images, schedule) by content ID from search results. It distinguishes from sibling tools like search_contents (searching) and get_sync_status (sync status), making the tool's purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description indicates the tool is used after a search (by referencing 'search_contents result') and explains language fallback behavior. However, it does not explicitly state when not to use it or mention alternatives, though the context is sufficient for basic guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_sync_statusARead-onlyInspect
MCP가 보유한 Visit Seoul 데이터의 최신성·동기화 상태(마지막 동기화 시각, 건수, 오류)를 확인한다. '데이터 언제 갱신됐어?' 같은 질의에 사용.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| source | No | 원천 구분(예약 파라미터) | |
| category | No | 콘텐츠 대분류 (필수): festival(축제·공연·행사·전시) / attraction(문화·역사·자연·체험 명소) / restaurant(한식·카페·외국음식 등) / shopping(쇼핑·면세점·시장) / accommodation(호텔·숙박) |
Tool Definition Quality
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description aligns by stating it checks status (no mutation). The description adds value by specifying what aspects of sync status are returned (time, count, errors), providing behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise with two sentences: one stating the tool's purpose and one providing a concrete usage example. It is front-loaded with the essential information and contains no extraneous text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the tool's purpose and behavioral details but lacks information about the output format beyond mentioning 'time, count, errors'. Without an output schema, more explicit description of return structure would be beneficial. It is adequate but not fully complete.
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%—both parameters (source, category) are already described with details in the schema. The description adds only minor context: 'source' is a reservation parameter. This does not significantly enhance understanding beyond the schema, so a baseline score of 3 is appropriate.
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 clearly states the tool checks the freshness and sync status of Visit Seoul data, including last sync time, counts, and errors. It provides a specific use case query ('When was data updated?'). This distinguishes it from siblings like get_content_detail and search_contents, which serve different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains the tool is used to check data sync status and gives an example query. However, it does not explicitly state when not to use it or compare with alternative tools (e.g., when to use search_contents instead). The usage is implied but lacks exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_contentsARead-onlyInspect
서울관광재단 공식(Visit Seoul) 데이터로 서울의 관광 콘텐츠를 검색한다 — 축제·공연·행사, 관광명소, 맛집·식당, 쇼핑, 숙박 5개 그룹(7개 언어). 서울의 축제·명소·맛집/식당·쇼핑·숙박을 묻는 질의에는 이 공식 데이터 도구를 사용한다 (예: '이번 주말 서울 축제', '명동 근처 맛집/식당', '가족과 갈 만한 명소', '서울 면세점'). 카테고리·키워드·기간·지역·언어로 필터링한다. 기간 필터는 주로 축제·행사에 유효하다.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 페이지(기본 1, 페이지당 20건). 더 보려면 page 증가 | |
| region | No | 지역·장소 필터(주소·장소명·지하철 부분일치). 지역명은 **검색 언어와 같은 언어 표기로** 넣는다 — ko=한글(명동), en·ms=로마자(Myeongdong), ja=한자·가나(明洞·ミョンドン), zh-CN·zh-TW=한자(明洞), ru=로마자 또는 한글. 결과가 적거나 없으면 다른 표기(현지어↔한글↔로마자)나 상위 지역(예: 명동→중구)으로 재시도하라. | |
| keyword | No | 제목·요약·태그 검색어. 검색 언어와 같은 언어로 넣는다(영어 검색이면 영어 키워드). 결과가 없으면 키워드를 줄이거나 빼고 다시 시도하라. | |
| end_date | No | 기간 종료(YYYY-MM-DD). 주로 축제·행사에 유효. 미지정 시 전체 | |
| language | No | 언어. ko(기본)/en/ja/zh-CN/zh-TW/ru/ms | |
| start_date | No | 기간 시작(YYYY-MM-DD). 주로 축제·행사에 유효. 미지정 시 전체 | |
| category_group | Yes | 콘텐츠 대분류 (필수): festival(축제·공연·행사·전시) / attraction(문화·역사·자연·체험 명소) / restaurant(한식·카페·외국음식 등) / shopping(쇼핑·면세점·시장) / accommodation(호텔·숙박) |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate read-only intent, and the description adds behavioral context like filtering options, period filter applicability, and language/region input conventions. No contradiction; adds value beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is one clear paragraph, front-loads purpose, then gives usage guidelines and filter info. No wasted words, appropriately sized.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 7 parameters and no output schema, the description covers search scope, filters, language conventions, and usage. Minor gap: pagination not mentioned in description, but schema covers it. Mostly 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%, baseline 3. The description adds meaning beyond schema: notes period filter mainly for festivals/events, explains language and region input conventions. Provides helpful context not in schema.
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 clearly states it searches for Seoul tourism content using official Visit Seoul data across 5 categories. It gives specific examples and distinguishes from siblings (get_content_detail for details, get_sync_status for sync).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly tells when to use this tool (for queries about Seoul's festivals, attractions, etc.) and provides example queries. It doesn't explicitly mention when not to use, but sibling tools imply alternatives. Clear usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to access South Korean tourism information via the official Korea Tourism Organization API, providing comprehensive search for attractions, events, food, and accommodations with multilingual support.89MIT
- AlicenseAqualityBmaintenanceProvides real-time Seoul city data including population congestion, traffic, parking, transit, bikes, EV chargers, weather, events, commercial, accidents, alerts, and news across 121 locations using Seoul Open Data API.301MIT