Skip to main content
Glama
korea-opendata-mcp

korea-opendata-mcp

by myungwoon

Get Subway Arrival

get_subway_arrival
Read-onlyIdempotent

Retrieves real-time train arrival information for a Seoul subway station, including line, direction, estimated arrival time, and current train position, with an optional line filter.

Instructions

서울 지하철역의 실시간 열차 도착 정보를 조회합니다 (호선, 방면, 도착 예정, 현재 위치).

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": {
      "station": "<station>"
    },
    "name": "get_subway_arrival"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNo호선 필터 (예: 2호선, 신분당선)
stationYes역 이름 (예: 강남, 서울역, 홍대입구)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds that the data is real-time, which usefully signals results are volatile and should not be treated as cached, but it says nothing about failure behavior for unknown or ambiguous station names.

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?

A single front-loaded sentence that wastes little space. The parenthetical listing of returned fields is mildly redundant given an output schema exists, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and complete annotations, much of the burden is lifted, and the description covers scope (Seoul subway) and data freshness. It nonetheless omits operational detail such as handling of ambiguous station names or unsupported lines, which matters for a lookup keyed on a free-text station.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters carry examples (강남 for station, 2호선 for line), so the schema already does the heavy lifting. The description only reiterates the line/direction concept without adding format or matching rules beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (retrieve real-time train arrival info for Seoul subway stations) and enumerates the data returned. It is unambiguously distinct from all siblings, which cover weather, air quality, holidays, and statistics, though it does not explicitly name any sibling.

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

Usage Guidelines2/5

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

The description says what the tool returns but gives no when-to-use guidance, no prerequisites, and no exclusions. The implicit 'real-time' framing suggests live queries, but nothing tells the agent how this differs from any alternative or when it would be inappropriate.

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