Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Search Tour Spots

search_tour_spots
Read-onlyIdempotent

Search Korean tourist attractions, restaurants, lodging, and cultural facilities by keyword to get addresses, phone numbers, coordinates, and representative images.

Instructions

키워드로 관광지·음식점·숙박·문화시설 등을 검색합니다 (주소, 전화, 좌표, 대표 이미지).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "search_tour_spots"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
keywordYes검색어 (예: 경복궁, 해운대, 한옥마을)
per_pageNo
content_typeNoall 전체 / attraction 관광지 / culture 문화시설 / festival 축제·행사 / course 여행코스 / leports 레포츠 / lodging 숙박 / shopping 쇼핑 / restaurant 음식점all

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without the description's help. The description adds only the returned field list (주소, 전화, 좌표, 대표 이미지), which is redundant given an output schema exists, and says nothing about pagination limits or result volume.

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?

A single front-loaded sentence with no filler. The only wasted fragment is the parenthetical return-field list, which duplicates what the output schema already provides and crowds out more useful information such as pagination behavior.

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?

With an output schema present the description need not explain return values, and it correctly stays brief. But for a 4-parameter search tool with a 1000-page ceiling and a capped per_page, the absence of any paging or result-count guidance leaves a real gap that the 50%-covered schema does not fill.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: keyword and content_type are documented in the schema, while page and per_page are bare integers with only min/max bounds. The description adds no pagination guidance and its category list (관광지·음식점·숙박·문화시설) covers only four of the nine content_type enum values, omitting festival, course, leports, and shopping, so it does not compensate for the gap.

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?

States a specific verb and resource: keyword search across tourist attractions, restaurants, lodging, and cultural facilities. The enumerated entity types make the resource concrete. It stops short of differentiating from sibling search_festivals, which overlaps with the festival category implicitly present in the content_type enum.

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?

Usage is implied by '키워드로 검색합니다' – the agent can infer this is the keyword-driven lookup for place-type data. However, there is no explicit when-to-use versus search_festivals, no mention of preferring a dedicated tool for a narrower category, and no exclusions.

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