Skip to main content
Glama
harimkang

Korea Tourism API MCP Server

get_detailed_information

Obtain comprehensive information about a Korean tourism item using its content ID. Returns address, description, images, contact, and type-specific details.

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
Behavior4/5

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

With no annotations provided, the description covers the retrieval nature and output structure comprehensively. It does not mention any side effects, authentication, or constraints, but for a simple read-oriented tool the transparency is adequate.

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 well-structured with Args, Returns, and Example sections. It is front-loaded with the purpose, and every sentence adds value. There is no redundancy or fluff.

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?

Despite no output schema, the description provides a detailed return structure with nested fields and an example call. All three parameters are fully explained, and the tool's behavior (combining common info, introduction, additional info) is explicitly stated.

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?

The schema provides only types and nullability with 0% description coverage. The description adds full semantics: content_id's purpose and source, content_type's valid values (8 options), and language's supported codes. This exceeds what schema offers.

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 retrieves detailed information about a specific tourism item in Korea by content ID, which is a specific verb+resource pairing. It implicitly distinguishes it from sibling tools that search or list items.

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 mentions the content_id is obtained from other search functions, implying a usage sequence. However, it does not explicitly list when to use this tool versus alternatives like find_accommodations or search_tourism_by_keyword.

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