Incheon Airport Transit MCP

airport_shuttle_next

Read-onlyIdempotent

[인천공항 대중교통] 인천공항 무료 셔틀버스 다음 도착 예측 시간(분).

공항 내부 이동용 무료 셔틀 (T1 ↔ T2 ↔ AICC ↔ 화물청사역 등). 실시간 60분 갱신.

Args:
    stop: 정류장 한글명(예: "제1여객터미널", "인천영종소방서") 또는 10자리 stopId. 빈값=전체.
    route: 노선 한글명(예: "AICC행", "AICC순환") 또는 8자리 routeId. 빈값=전체.
    lang: "ko"/"en".

Returns:
    {count, items: [{stop_name, route_name, eta_minutes, ofr_time, ord, raw}]}

Input Schema

TableJSON Schema

Name	Required	Default
`lang`	No	ko
`stop`	No
`route`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds that data is real-time with 60-minute updates, and explains the return structure. This adds value beyond the annotations.

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 description is concise, front-loaded with purpose, and structured with clear sections for Args and Returns. Every sentence contributes meaning without redundancy.

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?

The description covers purpose, parameters, output structure, and data freshness. For a simple read-only tool with no required parameters, this is nearly complete. Minor missing info (e.g., authentication) is not critical.

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?

With 0% schema description coverage, the description compensates fully by explaining each parameter: stop (name or ID, empty for all), route (name or ID, empty for all), and lang. Examples are provided, helping the agent use them correctly.

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 the tool predicts the next arrival time of the free shuttle at Incheon Airport. It specifies the scope (inside airport, T1↔T2↔AICC↔cargo terminal) and distinguishes from sibling tools like airport_bus and airport_shuttle_schedule.

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 implies use for real-time arrival predictions of free shuttles, and sibling names help differentiate. However, it does not explicitly state when not to use or suggest 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?