Incheon Airport Transit MCP

airport_bus

Read-onlyIdempotent

[인천공항 대중교통] 인천국제공항 ↔ 전국 공항버스 노선·시간표·요금·승차장.

데이터셋 갱신 60분. T1/T2 평일·주말 시간표 분리 제공. 버스 등급(일반/우등)·운수사 연락처 포함.

Args:
    region: 한글 권역명(서울/경기/인천/강원/충청/경상/전라) 또는 1~7 코드. 빈값=전체.
    search: 버스번호/운수사/정류장 키워드 부분일치 (예: "강남", "6009", "KAL").
    lang: "ko" (한글) 또는 "en" (영문 라벨 일부).

Returns:
    {count, area, items: [{busnumber, route, fare, busclass, cpname, terminal_first_last, route_info, ride_loc}]}

Input Schema

TableJSON Schema

Name	Required	Default
`lang`	No	ko
`region`	No
`search`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare readOnly, idempotent, non-destructive. Description adds update frequency, timetable separation, and return structure details, providing full transparency beyond annotations.

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?

Concise with a main sentence and structured Args section. Slightly verbose in listing details but overall efficient and well-organized.

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?

Given the output schema and annotations, the description is complete: purpose, update frequency, parameter details, and return structure are all covered.

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 has 0% per-parameter descriptions, but the description explains each parameter: region (Korean name or code 1-7, empty=all), search (partial match), lang (ko/en). This fully compensates for the lack of schema descriptions.

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 it provides airport bus routes, schedules, fares, and boarding locations for Incheon Airport to nationwide, distinguishing it from sibling tools like shuttle, taxi, and train.

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 gives context (dataset update every 60 minutes, separate weekday/weekend timetables) but lacks explicit when-to-use or alternatives vs. siblings. Purpose is clear enough for an AI to infer from tool name and sibling set.

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?