Skip to main content
Glama
harimkang

Korea Tourism API MCP Server

get_tourism_by_area

Retrieve tourism information for specific geographic areas in Korea by filtering area codes, districts, and content types to find attractions, events, accommodations, and more.

Instructions

Browse tourism information by geographic areas in Korea.

This tool retrieves tourism items from a specific geographic area in Korea. It allows filtering by area code, sigungu (district) code, and content type to find relevant tourism information in a particular region.

Args: area_code (str): Area code. Valid values: - "1" (Seoul) - "2" (Incheon) - "3" (Daejeon) - "4" (Daegu) - "5" (Gwangju) - "6" (Busan) - "7" (Ulsan) - "8" (Sejong) - "31" (Gyeonggi-do) - "32" (Gangwon-do) - "33" (Chungcheongbuk-do) - "34" (Chungcheongnam-do) - "35" (Gyeongsangbuk-do) - "36" (Gyeongsangnam-do) - "37" (Jeonbuk-do) - "38" (Jeollanam-do) - "39" (Jeju-do) sigungu_code (str, optional): Sigungu (district) code within the area content_type (str, optional): Type of content to filter. Valid values: - "Tourist Attraction" (default) - "Cultural Facility" - "Festival Event" - "Leisure Activity" - "Accommodation" - "Shopping" - "Restaurant" - "Transportation" language (str, optional): Language for results (default: "en"). Supported: - "en" (English) - "jp" (Japanese) - "zh-cn" (Simplified Chinese) - "zh-tw" (Traditional Chinese) - "de" (German) - "fr" (French) - "es" (Spanish) - "ru" (Russian) page (int, optional): Page number for pagination (default: 1, min: 1) rows (int, optional): Number of items per page (default: 20, max: 100) filter (list[str], optional): List of keys to include in each result item (whitelist). - If filter is None or an empty list ([]), all fields are returned. - If filter contains values, only the specified keys will be included in each item, and all other keys will be removed.

Returns: dict: Area-based tourism information with structure: { "total_count": int, # Total number of matching items "num_of_rows": int, # Number of items per page "page_no": int, # Current page number "items": [ # List of tourism items { "title": str, # Name of the attraction/place "addr1": str, # Primary address "addr2": str, # Secondary address "areacode": str, # Area code "sigungucode": str, # Sigungu code "cat1": str, # Category 1 code "cat2": str, # Category 2 code "cat3": str, # Category 3 code "contentid": str, # Unique content ID "contenttypeid": str, # Content type ID "createdtime": str, # Creation timestamp "modifiedtime": str, # Last modified timestamp "tel": str, # Phone number "firstimage": str, # URL of main image "firstimage2": str, # URL of thumbnail image "mapx": str, # Longitude "mapy": str, # Latitude "zipcode": str, # Postal code "mlevel": str # Map level } # ... more items ] }

Example: get_tourism_by_area("1", "1", "Tourist Attraction", "en", 1, 20)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
area_codeYes
sigungu_codeNo
content_typeNo
languageNo
pageNo
rowsNo
filterNo

Implementation Reference

  • The function 'get_tourism_by_area' implements the logic to fetch tourism data from the Korea Tourism API based on area and category filters.
    async def get_tourism_by_area(
        area_code: str,
        sigungu_code: str | None = None,
        content_type: str | None = None,
        language: str | None = None,
        page: int = 1,
        rows: int = 20,
        filter: list[str] | None = None,
    ) -> dict:
        """
        Browse tourism information by geographic areas in Korea.
    
        This tool retrieves tourism items from a specific geographic area in Korea.
        It allows filtering by area code, sigungu (district) code, and content type
        to find relevant tourism information in a particular region.
    
        Args:
            area_code (str): Area code. Valid values:
                - "1" (Seoul)
                - "2" (Incheon)
                - "3" (Daejeon)
                - "4" (Daegu)
                - "5" (Gwangju)
                - "6" (Busan)
                - "7" (Ulsan)
                - "8" (Sejong)
                - "31" (Gyeonggi-do)
                - "32" (Gangwon-do)
                - "33" (Chungcheongbuk-do)
                - "34" (Chungcheongnam-do)
                - "35" (Gyeongsangbuk-do)
                - "36" (Gyeongsangnam-do)
                - "37" (Jeonbuk-do)
                - "38" (Jeollanam-do)
                - "39" (Jeju-do)
            sigungu_code (str, optional): Sigungu (district) code within the area
            content_type (str, optional): Type of content to filter. Valid values:
                - "Tourist Attraction" (default)
                - "Cultural Facility"
                - "Festival Event"
                - "Leisure Activity"
                - "Accommodation"
                - "Shopping"
                - "Restaurant"
                - "Transportation"
            language (str, optional): Language for results (default: "en"). Supported:
                - "en" (English)
                - "jp" (Japanese)
                - "zh-cn" (Simplified Chinese)
                - "zh-tw" (Traditional Chinese)
                - "de" (German)
                - "fr" (French)
                - "es" (Spanish)
                - "ru" (Russian)
            page (int, optional): Page number for pagination (default: 1, min: 1)
            rows (int, optional): Number of items per page (default: 20, max: 100)
            filter (list[str], optional): List of keys to include in each result item (whitelist).
                - If filter is None or an empty list ([]), all fields are returned.
                - If filter contains values, only the specified keys will be included in each item, and all other keys will be removed.
    
        Returns:
            dict: Area-based tourism information with structure:
            {
                "total_count": int,     # Total number of matching items
                "num_of_rows": int,     # Number of items per page
                "page_no": int,         # Current page number
                "items": [              # List of tourism items
                    {
                        "title": str,           # Name of the attraction/place
                        "addr1": str,           # Primary address
                        "addr2": str,           # Secondary address
                        "areacode": str,        # Area code
                        "sigungucode": str,     # Sigungu code
                        "cat1": str,            # Category 1 code
                        "cat2": str,            # Category 2 code
                        "cat3": str,            # Category 3 code
                        "contentid": str,       # Unique content ID
                        "contenttypeid": str,   # Content type ID
                        "createdtime": str,     # Creation timestamp
                        "modifiedtime": str,    # Last modified timestamp
                        "tel": str,             # Phone number
                        "firstimage": str,      # URL of main image
                        "firstimage2": str,     # URL of thumbnail image
                        "mapx": str,            # Longitude
                        "mapy": str,            # Latitude
                        "zipcode": str,         # Postal code
                        "mlevel": str           # Map level
                    }
                    # ... more items
                ]
            }
    
        Example:
            get_tourism_by_area("1", "1", "Tourist Attraction", "en", 1, 20)
        """
        # Validate and convert content_type
        content_type_id = None
        if content_type:
            content_type_id = next(
                (
                    k
                    for k, v in CONTENTTYPE_ID_MAP.items()
                    if v.lower() == content_type.lower()
                ),
                None,
            )
            if content_type_id is None:
                valid_types = ", ".join(CONTENTTYPE_ID_MAP.values())
                raise ValueError(
                    f"Invalid content_type: '{content_type}'. Valid types are: {valid_types}"
                )
    
        # Call the API client and return dict directly
        result = await get_api_client().get_area_based_list(
            area_code=area_code,
            sigunguCode=sigungu_code,
            content_type_id=content_type_id,
            language=language,
            page=page,
            rows=rows,
        )
        if filter:
            # Apply additional filtering if provided
            filter_items = []
            for item in result.get("items", []):
                item = {k: v for k, v in item.items() if k in filter}
                filter_items.append(item)
            result["items"] = filter_items
        return result
  • The 'get_tourism_by_area' tool is registered with the MCP server using the '@mcp.tool' decorator.
    @mcp.tool
    async def get_tourism_by_area(
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing: pagination behavior (page/rows parameters), filtering mechanics (whitelist approach), default values, and response structure. It doesn't mention rate limits, authentication needs, or error conditions, but provides substantial operational transparency.

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?

Well-structured with purpose statement, parameter documentation, return format, and example. Some redundancy exists (e.g., 'Browse tourism information...' then 'This tool retrieves...'), and the parameter section is lengthy but necessary given schema coverage. Overall efficient for the complexity.

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 7-parameter tool with no annotations and 0% schema coverage, the description provides comprehensive documentation: clear purpose, detailed parameter semantics, return structure, and example. It addresses all essential aspects despite the lack of structured metadata, making it complete for agent understanding.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation: all 7 parameters are explained with valid values, defaults, and behavioral implications (especially the 'filter' parameter's whitelist logic). This adds significant value beyond the bare 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 the tool's purpose: 'retrieves tourism items from a specific geographic area in Korea' with filtering capabilities. It specifies the resource (tourism information), geographic scope (Korea), and distinguishes it from siblings like 'search_tourism_by_keyword' (keyword-based) or 'find_nearby_attractions' (proximity-based).

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 implies usage context through parameter explanations (filtering by area, district, content type) but doesn't explicitly state when to use this tool versus alternatives like 'search_tourism_by_keyword' or 'find_nearby_attractions'. It provides operational guidance but lacks comparative decision criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/harimkang/mcp-korea-tourism-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server