12306-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get-current-dateA | 获取当前日期，以上海时区（Asia/Shanghai, UTC+8）为准，返回格式为 "yyyy-MM-dd"。主要用于解析用户提到的相对日期（如“明天”、“下周三”），为其他需要日期的接口提供准确的日期输入。 |
| get-stations-code-in-cityA | 通过中文城市名查询该城市 所有 火车站的名称及其对应的 |
| get-station-code-of-citysA | 通过中文城市名查询代表该城市的 |
| get-station-code-by-namesA | 通过具体的中文车站名查询其 |
| get-station-by-telecodeA | 通过车站的 |
| get-ticketsB | 查询12306余票信息。 |
| get-interline-ticketsB | 查询12306中转余票信息。尚且只支持查询前十条。 |
| get-train-route-stationsA | 查询特定列车车次在指定区间内的途径车站、到站时间、出发时间及停留时间等详细经停信息。当用户询问某趟具体列车的经停站时使用此接口。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| stations |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no overlap. Tools target specific functions like date retrieval, station code lookup (by telecode, names, cities, or stations in a city), ticket queries (direct and interline), and train route details, making misselection unlikely.
All tools follow a consistent verb_noun pattern with 'get-' prefix (e.g., get-current-date, get-tickets). The naming is uniform and predictable, enhancing readability and usability.
With 8 tools, the server is well-scoped for querying 12306 train data. Each tool serves a specific role in the workflow, from station code resolution to ticket and route queries, without being overly sparse or bloated.
The toolset covers core functionalities like date handling, station code retrieval, ticket queries, and route details, supporting key user workflows. A minor gap is the lack of booking or purchase tools, but this is reasonable for a query-focused server.