Skip to main content
Glama
harimkang

Korea Tourism API MCP Server

get_detailed_information

Retrieve comprehensive details about Korean tourism items including attractions, accommodations, restaurants, and events using content IDs. Provides multilingual information with addresses, descriptions, operating hours, and additional data for trip planning.

Instructions

Get detailed information about a specific tourism item in Korea.

This tool retrieves comprehensive details about a specific tourism item by its content ID. It combines common information, introduction details, and additional information to provide a complete picture of the tourism item.

Args: content_id (str): Content ID of the tourism item (obtained from other search functions) content_type (str, optional): Type of content. Valid values: - "Tourist Attraction" - "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)

Returns: dict: Detailed information with structure: { # Common information "title": str, # Name of the item "contentid": str, # Unique content ID "contenttypeid": str, # Content type ID "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 "mapx": str, # Longitude "mapy": str, # Latitude "mlevel": str, # Map level "overview": str, # Detailed description "tel": str, # Phone number "telname": str, # Contact name "homepage": str, # Website URL "firstimage": str, # URL of main image "firstimage2": str, # URL of thumbnail image "createdtime": str, # Creation timestamp "modifiedtime": str, # Last modified timestamp "zipcode": str, # Postal code

    # Introduction details (varies by content type)
    "infocenter": str,      # Information center (for attractions)
    "restdate": str,        # Rest/closing days
    "usetime": str,         # Hours of operation
    "parking": str,         # Parking information
    # ... other type-specific fields

    # Additional information
    "additional_info": [    # List of additional details
        {
            "infoname": str,    # Name of the information
            "infotext": str,    # Detailed text information
            "fldgubun": str,    # Field division code
            "serialnum": str    # Serial number
        }
        # ... more items
    ]
}

Example: get_detailed_information("126508", "Tourist Attraction", "en")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
content_idYes
content_typeNo
languageNo

Implementation Reference

  • The get_detailed_information tool implementation decorated with @mcp.tool, which fetches, combines, and returns detailed information about a tourism item.
    @mcp.tool
    async def get_detailed_information(
        content_id: str,
        content_type: str | None = None,
        language: str | None = None,
    ) -> dict:
        """
        Get detailed information about a specific tourism item in Korea.
    
        This tool retrieves comprehensive details about a specific tourism item by its
        content ID. It combines common information, introduction details, and additional
        information to provide a complete picture of the tourism item.
    
        Args:
            content_id (str): Content ID of the tourism item (obtained from other search functions)
            content_type (str, optional): Type of content. Valid values:
                - "Tourist Attraction"
                - "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)
    
        Returns:
            dict: Detailed information with structure:
            {
                # Common information
                "title": str,           # Name of the item
                "contentid": str,       # Unique content ID
                "contenttypeid": str,   # Content type ID
                "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
                "mapx": str,            # Longitude
                "mapy": str,            # Latitude
                "mlevel": str,          # Map level
                "overview": str,        # Detailed description
                "tel": str,             # Phone number
                "telname": str,         # Contact name
                "homepage": str,        # Website URL
                "firstimage": str,      # URL of main image
                "firstimage2": str,     # URL of thumbnail image
                "createdtime": str,     # Creation timestamp
                "modifiedtime": str,    # Last modified timestamp
                "zipcode": str,         # Postal code
    
                # Introduction details (varies by content type)
                "infocenter": str,      # Information center (for attractions)
                "restdate": str,        # Rest/closing days
                "usetime": str,         # Hours of operation
                "parking": str,         # Parking information
                # ... other type-specific fields
    
                # Additional information
                "additional_info": [    # List of additional details
                    {
                        "infoname": str,    # Name of the information
                        "infotext": str,    # Detailed text information
                        "fldgubun": str,    # Field division code
                        "serialnum": str    # Serial number
                    }
                    # ... more items
                ]
            }
    
        Example:
            get_detailed_information("126508", "Tourist Attraction", "en")
        """
        # 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}"
                )
    
        # Get common details
        common_details = await get_api_client().get_detail_common(
            content_id=content_id,
            language=language,
        )
    
        # Get intro details if content_type_id is provided
        intro_details: Dict[str, Any] = {}
        if content_type_id:
            intro_result = await get_api_client().get_detail_intro(
                content_id=content_id, content_type_id=content_type_id, language=language
            )
            intro_details = (
                intro_result.get("items", [{}])[0] if intro_result.get("items") else {}
            )
    
        # Get additional details
        additional_details: Dict[str, Any] = {}
        if content_type_id:
            additional_result = await get_api_client().get_detail_info(
                content_id=content_id, content_type_id=content_type_id, language=language
            )
            additional_details = {"additional_info": additional_result.get("items", [])}
    
        # Combine all details
        item = common_details.get("items", [{}])[0] if common_details.get("items") else {}
        return {**item, **intro_details, **additional_details}
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by explaining what information is returned (common details, introduction details, additional info), the structure of the return data, and language support. However, it doesn't mention rate limits, authentication requirements, error conditions, or whether this is a read-only operation (though 'get' implies it likely is).

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 well-structured with clear sections (purpose, args, returns, example) and efficiently communicates necessary information. However, the returns section is quite lengthy with extensive field documentation that might be better suited for an output schema. The core purpose is front-loaded appropriately.

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?

For a tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description does an excellent job of providing context. It documents all parameters thoroughly, explains the return structure in detail, and provides a clear example. The main gap is lack of behavioral context like rate limits or error handling.

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. It explains content_id is 'obtained from other search functions', lists all valid values for content_type with clear examples, specifies the default language and all supported language codes. This adds significant meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves comprehensive details about a specific tourism item by content ID, combining common information, introduction details, and additional information. It specifies the resource (tourism item in Korea) and verb (get detailed information), but doesn't explicitly distinguish it from sibling tools like 'get_tourism_by_area' or 'search_tourism_by_keyword' which might also return tourism information.

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 by mentioning the content ID is 'obtained from other search functions' and provides an example, suggesting it should be used after search tools. However, it doesn't explicitly state when to use this vs. alternatives like 'find_nearby_attractions' or 'get_tourism_images', nor does it mention any prerequisites or exclusions beyond needing a content ID.

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