Skip to main content
Glama

Korea Travel Demand & Price Archive (요즘인기여행)

Hanatour package ranking by bookings, 2nd demand source (하나투어 예약순 상위 20)

get_hanatour_ranking
Read-onlyIdempotent

Second, independent demand signal (from 2026-10-21): for each popular city, the top-20 overseas packages on Hanatour (Korea's largest travel agency) sorted by the site's own "most booked" order, with cumulative review counts, ratings, adult-min prices, departure-fixed flags, the number of packages on sale per city, and the site's top-10 search keywords with search counts; each with 30-day history. Ordinal rank only (no absolute booking counts) — do not merge with the Naver buyer index; read trends separately. Omit city for an all-cities summary. 하나투어 도시별 예약순 상위 20(순위·누적 후기·평점·최저가·출발확정)·판매 상품 수·인기 검색어 10. 네이버 구매 인원과 다른 종류의 신호라 합산 금지.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hanatour_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo도시: 한글(오사카·하노이·방콕), 영문(osaka·hanoi·bangkok) 또는 인천 출발 도착 공항코드(KIX·HAN·BKK)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, and the description adds genuinely non-obvious behavior: values are ordinal rank only with no absolute booking counts, data is a dated snapshot (2026-10-21), and each item carries 30-day history. The 'do not merge with Naver buyer index' caveat is a real analytical trap it warns about.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and informative, but the entire Korean sentence restates the English text, roughly doubling length with little added information beyond localized search terms. Dense single-sentence packing of a dozen return fields also makes it harder to scan.

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?

With no output schema, the description compensates by enumerating what comes back (rank, cumulative reviews, rating, adult-min price, departure-fixed flags, per-city package counts, top-10 search keywords, 30-day history). Combined with scope and data vintage, an agent has everything needed to call and interpret it correctly.

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% (the city param already documents Korean/English/airport-code forms), so baseline is 3. The description adds the behavioral default — omitting city yields an all-cities summary — which is meaning the schema's optional/not-required status alone does not convey.

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?

Names a specific resource (top-20 Hanatour packages per city, ranked by the site's own booking order) plus the exact fields returned and the dataset vintage. It also explicitly distinguishes itself from the Naver buyer index, so an agent can separate it from get_demand_index without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete usage rules: omit city for an all-cities summary, read trends separately from the Naver index, and don't merge the two signals. That is an explicit when-to-use plus a when-not-to-use/alternative condition, which is the top of the scale.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources