Incheon Airport Transit MCP

airport_shuttle_schedule

Read-onlyIdempotent

[인천공항 대중교통] 인천공항 무료 셔틀버스 시간표 (의미 단위 요약).

노선별 평일/휴일 첫차·막차·배차 간격·운행 편수 + 종점 출발 시각 전체 + 첫편의
정류장 순서별 통과 시각. 정류장×편수 raw row 노출 (수백~수천 건) 대신 사용자
관점에서 직접 의미 있는 단위로 압축.

데이터셋 갱신 60분. 참고: 현재 시간표 dataset 에는 'AICC행' (routeId 11100001,
11100006) 두 노선만 등록되어 있어 그 외 노선(AICC순환/T1행/T2행/T2직행/
화물청사역행/T1막차)을 필터하면 빈 결과가 정상. 도착 예측은
airport_shuttle_next 가 모든 노선 커버.

Args:
    route: 노선 한글명(예: "AICC행") 또는 8자리 routeId. 빈값=노선 목록만 요약.
    day: "weekday" (평일) / "holiday" (휴일) / "all" (전체, 기본).
    lang: "ko"/"en".

Returns:
    route 빈값 시: {count, routes: [{route_id, route_name, weekday_departures, holiday_departures}]}
    route 지정 시: {route_id, route_name, day_filter, by_day: {
        weekday/holiday: {
            day_type_kr, departure_count, first_departure, last_departure,
            interval_avg, all_departures: [HH:MM,...],
            first_trip_stops: [{stop_order, stop_name, time}, ...]
        }
    }}

Input Schema

TableJSON Schema

Name	Required	Default
`day`	No	all
`lang`	No	ko
`route`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds dataset refresh interval (60 min), behavior for missing routes, and return format details, providing extra context without contradiction.

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?

Description is detailed but lengthy; it could be more concise. However, it is well-organized with clear sections and front-loaded summary.

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?

Covers all relevant aspects: behavior, limitations, relation to sibling tools, and return format. Output schema exists, so return value explanation is sufficient.

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?

Schema coverage is 0%, but description thoroughly explains each parameter ('route', 'day', 'lang') with examples and defaults, adding necessary meaning beyond the schema.

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?

Description clearly states it summarizes Incheon Airport free shuttle bus schedules, including first/last bus, intervals, and stop times. It distinguishes itself from sibling tools by noting coverage and limitations.

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?

Explicitly mentions that only two routes are in the dataset, and that arrival prediction is handled by 'airport_shuttle_next', guiding when to use this tool vs alternatives.

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

All Incheon Airport Transit MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool addresses a distinct mode of transit (bus, shuttle real-time, shuttle schedule, taxi, train) with clear descriptions, leaving no ambiguity for an agent.

Naming Consistency5/5

All tool names follow a consistent `airport_<transport_type>` pattern, with shuttle tools further differentiated by `_next` and `_schedule` suffixes, making them predictable.

Tool Count5/5

With 5 tools covering bus, shuttle (real-time and schedule), taxi, and train, the count is well-scoped for an airport transit information server.

Completeness5/5

The tool set covers all major transit modes to/from and within Incheon Airport, including real-time and schedule data, with no obvious gaps.

Resources

Need Help?