K-Targo Subway MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOV_API_KEY | Yes | Your public data API key from https://www.data.go.kr/ for the 국토교통부_(TAGO)_지하철정보 API |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_subway_stationA | 지하철역 이름으로 역 정보를 검색합니다. 역 ID, 역 이름, 노선 정보를 반환합니다. '역' 접미사는 자동으로 제거됩니다 (예: '강남역' → '강남'). |
| get_subway_timetableC | 지하철역의 시간표를 조회합니다. 요일별, 상하행별 시간표를 제공합니다. |
| get_all_subway_timetablesC | 지하철역의 모든 요일, 모든 방향의 시간표를 한 번에 조회합니다. 평일/토요일/일요일, 상행/하행 모든 조합을 제공합니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_all_subway_timetables retrieves comprehensive timetables for all days and directions, get_subway_timetable provides filtered timetables by day and direction, and search_subway_station finds station information. There is no overlap or ambiguity between these functions.
All tool names follow a consistent snake_case pattern with a clear verb_noun structure: get_all_subway_timetables, get_subway_timetable, and search_subway_station. The naming is predictable and readable throughout.
With only 3 tools, the server feels thin for a subway domain that might benefit from additional operations like route planning or real-time status. However, the tools cover core timetable and station search functions, making it borderline but functional.
The tools provide good coverage for timetable retrieval and station search, but there are minor gaps such as missing operations for route calculation, fare information, or real-time updates. Agents can work around these with the available tools for basic queries.