Big Data Insights for Regional Inflow in Korea

get_datalab_daily

한국관광 데이터랩 시군구별 '일별' 방문자 수(사람 수 추정, 단위 '명')와 그 지역의 요일·장날 리듬을 돌려준다.

- 나우캐스트(주 단위, 이동 '건')와 단위가 다르다. 둘을 더하거나 섞지 말 것.
- 방문 지표로는 외지인을 쓸 것. 현지인은 그 지역 상주자(거주·근무·통학)라 방문 지표가 아니다.
- 외지인에는 근무자가 빠져 있어 출퇴근이 많은 지역(업무지구)은 이 자료로 가릴 수 없다.
- 일 단위라 하루짜리 행사(야구 경기, 불꽃축제, 태풍)를 확인하는 데 쓸 것. 최소 단위는 시군구(읍면동 없음).
- start_date·end_date: YYYY-MM-DD, 최대 400일. 자료는 약 한 달 늦게 나오고 최근 값은 소급 수정될 수 있다.

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": {
      "sido": "<sido>",
      "sigungu": "<sigungu>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_datalab_daily"
  }
}

Input Schema

Name	Required	Default
`kind`	No	외지인
`sido`	Yes
`sigungu`	Yes
`end_date`	Yes
`start_date`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.4/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose several important traits: roughly one-month publication lag, possible retroactive revision of recent values, a 400-day cap, a sigungu-only minimum granularity, and the fact that 외지인 omits workers. However, it never states authentication or rate-limit needs, whether the call is read-only, or the shape of the returned payload (fields, ordering, missing-day handling), which leaves a mutation-adjacent operational profile unstated.

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 return value and its unit lead, followed by short bullets each carrying a distinct constraint (unit mismatch, metric choice, coverage gap, granularity, parameter format). No sentence is redundant and the most decision-relevant information is front-loaded.

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 five-parameter, no-annotation, no-output-schema data tool, the description covers units, granularity, latency, revision behavior, and caveats well. The remaining gaps are the input identifier format for sido/sigungu and any indication of the returned record structure, minor but real for an agent building a correct call.

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 description coverage is 0%, so the description must compensate, and it does for the date range (YYYY-MM-DD, max 400 days) and for the kind enum's semantics (외지인 as visit metric, 현지인 as residents). It still gives no format guidance for sido/sigungu — names versus administrative codes — which is a notable gap at zero coverage, and 외국인 is left unexplained.

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 states a specific verb and resource: it returns daily visitor counts (estimated persons, unit '명') by sigungu plus that region's weekday/market-day rhythm. It explicitly distinguishes itself from the weekly '나우캐스트' movement data by unit ('명' vs '건'), so an agent can tell the two apart without opening either 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?

Usage is prescribed explicitly: use 외지인 as the visit metric, do not use 현지인 (residents), use this data to check single-day events (baseball games, fireworks, typhoons), and do not add or mix it with 나우캐스트. It also states a hard exclusion — 업무지구 with heavy commuting cannot be judged from this data — which is genuine when-not guidance.

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

All Big Data Insights for Regional Inflow in Korea tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?