Skip to main content
Glama
Joooook

12306-mcp

by Joooook
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

get-tickets

Query real-time train ticket availability on 12306 by date and stations. Filter by train type, time range, and sort results. Get output in text, CSV, or JSON.

Instructions

查询12306余票信息。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes查询日期，格式为 "yyyy-MM-dd"。如果用户提供的是相对日期（如“明天”），请务必先调用 `get-current-date` 接口获取当前日期，并计算出目标日期。
fromStationYes出发地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）
toStationYes到达地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）
trainFilterFlagsNo车次筛选条件，默认为空，即不筛选。支持多个标志同时筛选。例如用户说“高铁票”，则应使用 "G"。可选标志：[G(高铁/城际),D(动车),Z(直达特快),T(特快),K(快速),O(其他),F(复兴号),S(智能动车组)]
earliestStartTimeNo最早出发时间（0-24），默认为0。
latestStartTimeNo最迟出发时间（0-24），默认为24。
sortFlagNo排序方式，默认为空，即不排序。仅支持单一标识。可选标志：[startTime(出发时间从早到晚), arriveTime(抵达时间从早到晚), duration(历时从短到长)]
sortReverseNo是否逆向排序结果，默认为false。仅在设置了sortFlag时生效。
limitedNumNo返回的余票数量限制，默认为0，即不限制。
formatNo返回结果格式，默认为text，建议使用text与csv。可选标志：[text, csv, json]text

Implementation Reference

  • src/index.ts:954-1138 (registration)
    Tool registration for 'get-tickets' via server.tool(), defining the MCP tool name, description, Zod schema for inputs, and the async handler.
    server.tool(
    'get-tickets',
    '查询12306余票信息。',
    {
        date: z
            .string()
            .length(10)
            .describe(
                '查询日期，格式为 "yyyy-MM-dd"。如果用户提供的是相对日期（如“明天”），请务必先调用 `get-current-date` 接口获取当前日期，并计算出目标日期。'
            ),
        fromStation: z
            .string()
            .describe(
                '出发地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）'
            ),
        toStation: z
            .string()
            .describe(
                '到达地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）'
            ),
        trainFilterFlags: z
            .string()
            .regex(/^[GDZTKOFS]*$/)
            .max(8)
            .optional()
            .default('')
            .describe(
                '车次筛选条件，默认为空，即不筛选。支持多个标志同时筛选。例如用户说“高铁票”，则应使用 "G"。可选标志：[G(高铁/城际),D(动车),Z(直达特快),T(特快),K(快速),O(其他),F(复兴号),S(智能动车组)]'
            ),
        earliestStartTime: z
            .number()
            .min(0)
            .max(24)
            .optional()
            .default(0)
            .describe('最早出发时间（0-24），默认为0。'),
        latestStartTime: z
            .number()
            .min(0)
            .max(24)
            .optional()
            .default(24)
            .describe('最迟出发时间（0-24），默认为24。'),
        sortFlag: z
            .string()
            .optional()
            .default('')
            .describe(
                '排序方式，默认为空，即不排序。仅支持单一标识。可选标志：[startTime(出发时间从早到晚), arriveTime(抵达时间从早到晚), duration(历时从短到长)]'
            ),
        sortReverse: z
            .boolean()
            .optional()
            .default(false)
            .describe(
                '是否逆向排序结果，默认为false。仅在设置了sortFlag时生效。'
            ),
        limitedNum: z
            .number()
            .min(0)
            .optional()
            .default(0)
            .describe('返回的余票数量限制，默认为0，即不限制。'),
        format: z
            .string()
            .regex(/^(text|csv|json)$/i)
            .default('text')
            .optional()
            .describe(
                '返回结果格式，默认为text，建议使用text与csv。可选标志：[text, csv, json]'
            ),
    },
    async ({
        date,
        fromStation,
        toStation,
        trainFilterFlags,
        earliestStartTime,
        latestStartTime,
        sortFlag,
        sortReverse,
        limitedNum,
        format,
    }) => {
        // 检查日期是否早于当前日期
        if (!checkDate(date)) {
            return {
                content: [
                    {
                        type: 'text',
                        text: 'Error: The date cannot be earlier than today.',
                    },
                ],
            };
        }
        const fromStationResult = parseStationCode(fromStation);
        const toStationResult = parseStationCode(toStation);
        if (fromStationResult === null || toStationResult === null) {
            return {
                content: [
                    {
                        type: 'text',
                        text: `Error: Station not found. FromStationResult: ${fromStationResult}, ToStationResult: ${toStationResult}.`,
                    },
                ],
            };
        }
        fromStation = fromStationResult;
        toStation = toStationResult;
        const queryParams = new URLSearchParams({
            'leftTicketDTO.train_date': date,
            'leftTicketDTO.from_station': fromStation,
            'leftTicketDTO.to_station': toStation,
            purpose_codes: 'ADULT',
        });
        const queryUrl = `${API_BASE}/otn/leftTicket/query`;
        const cookies = await getCookie();
        if (cookies == null || Object.entries(cookies).length === 0) {
            return {
                content: [
                    {
                        type: 'text',
                        text: 'Error: get cookie failed. Check your network.',
                    },
                ],
            };
        }
        const queryResponse = await make12306Request<LeftTicketsQueryResponse>(
            queryUrl,
            queryParams,
            { Cookie: formatCookies(cookies) }
        );
        if (queryResponse === null || queryResponse === undefined) {
            return {
                content: [
                    { type: 'text', text: 'Error: get tickets data failed. ' },
                ],
            };
        }
        const ticketsData = parseTicketsData(queryResponse.data.result);
        let ticketsInfo: TicketInfo[];
        try {
            ticketsInfo = parseTicketsInfo(ticketsData, queryResponse.data.map);
        } catch (error) {
            console.error('Error: parse tickets info failed. ', error);
            return {
                content: [
                    {
                        type: 'text',
                        text: 'Error: parse tickets info failed. ',
                    },
                ],
            };
        }
        const filteredTicketsInfo = filterTicketsInfo<TicketInfo>(
            ticketsInfo,
            trainFilterFlags,
            earliestStartTime,
            latestStartTime,
            sortFlag,
            sortReverse,
            limitedNum
        );
        var formatedResult;
        switch (format) {
            case 'csv':
                formatedResult = formatTicketsInfoCSV(filteredTicketsInfo);
                break;
            case 'json':
                formatedResult = JSON.stringify(filteredTicketsInfo);
                break;
            default:
                formatedResult = formatTicketsInfo(filteredTicketsInfo);
                break;
        }
        return {
            content: [
                {
                    type: 'text',
                    text: formatedResult,
                },
            ],
        };
    }
);
  • src/index.ts:1026-1137 (handler)
    Main handler logic for get-tickets: validates date, parses station codes, queries 12306 API, parses ticket data, filters/sorts results, and formats output.
    async ({
    date,
    fromStation,
    toStation,
    trainFilterFlags,
    earliestStartTime,
    latestStartTime,
    sortFlag,
    sortReverse,
    limitedNum,
    format,
}) => {
    // 检查日期是否早于当前日期
    if (!checkDate(date)) {
        return {
            content: [
                {
                    type: 'text',
                    text: 'Error: The date cannot be earlier than today.',
                },
            ],
        };
    }
    const fromStationResult = parseStationCode(fromStation);
    const toStationResult = parseStationCode(toStation);
    if (fromStationResult === null || toStationResult === null) {
        return {
            content: [
                {
                    type: 'text',
                    text: `Error: Station not found. FromStationResult: ${fromStationResult}, ToStationResult: ${toStationResult}.`,
                },
            ],
        };
    }
    fromStation = fromStationResult;
    toStation = toStationResult;
    const queryParams = new URLSearchParams({
        'leftTicketDTO.train_date': date,
        'leftTicketDTO.from_station': fromStation,
        'leftTicketDTO.to_station': toStation,
        purpose_codes: 'ADULT',
    });
    const queryUrl = `${API_BASE}/otn/leftTicket/query`;
    const cookies = await getCookie();
    if (cookies == null || Object.entries(cookies).length === 0) {
        return {
            content: [
                {
                    type: 'text',
                    text: 'Error: get cookie failed. Check your network.',
                },
            ],
        };
    }
    const queryResponse = await make12306Request<LeftTicketsQueryResponse>(
        queryUrl,
        queryParams,
        { Cookie: formatCookies(cookies) }
    );
    if (queryResponse === null || queryResponse === undefined) {
        return {
            content: [
                { type: 'text', text: 'Error: get tickets data failed. ' },
            ],
        };
    }
    const ticketsData = parseTicketsData(queryResponse.data.result);
    let ticketsInfo: TicketInfo[];
    try {
        ticketsInfo = parseTicketsInfo(ticketsData, queryResponse.data.map);
    } catch (error) {
        console.error('Error: parse tickets info failed. ', error);
        return {
            content: [
                {
                    type: 'text',
                    text: 'Error: parse tickets info failed. ',
                },
            ],
        };
    }
    const filteredTicketsInfo = filterTicketsInfo<TicketInfo>(
        ticketsInfo,
        trainFilterFlags,
        earliestStartTime,
        latestStartTime,
        sortFlag,
        sortReverse,
        limitedNum
    );
    var formatedResult;
    switch (format) {
        case 'csv':
            formatedResult = formatTicketsInfoCSV(filteredTicketsInfo);
            break;
        case 'json':
            formatedResult = JSON.stringify(filteredTicketsInfo);
            break;
        default:
            formatedResult = formatTicketsInfo(filteredTicketsInfo);
            break;
    }
    return {
        content: [
            {
                type: 'text',
                text: formatedResult,
            },
        ],
    };
}
  • src/index.ts:957-1025 (schema)
    Zod input schema for get-tickets defining parameters: date, fromStation, toStation, trainFilterFlags, earliestStartTime, latestStartTime, sortFlag, sortReverse, limitedNum, format.
    {
    date: z
        .string()
        .length(10)
        .describe(
            '查询日期，格式为 "yyyy-MM-dd"。如果用户提供的是相对日期（如“明天”），请务必先调用 `get-current-date` 接口获取当前日期，并计算出目标日期。'
        ),
    fromStation: z
        .string()
        .describe(
            '出发地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）'
        ),
    toStation: z
        .string()
        .describe(
            '到达地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）'
        ),
    trainFilterFlags: z
        .string()
        .regex(/^[GDZTKOFS]*$/)
        .max(8)
        .optional()
        .default('')
        .describe(
            '车次筛选条件，默认为空，即不筛选。支持多个标志同时筛选。例如用户说“高铁票”，则应使用 "G"。可选标志：[G(高铁/城际),D(动车),Z(直达特快),T(特快),K(快速),O(其他),F(复兴号),S(智能动车组)]'
        ),
    earliestStartTime: z
        .number()
        .min(0)
        .max(24)
        .optional()
        .default(0)
        .describe('最早出发时间（0-24），默认为0。'),
    latestStartTime: z
        .number()
        .min(0)
        .max(24)
        .optional()
        .default(24)
        .describe('最迟出发时间（0-24），默认为24。'),
    sortFlag: z
        .string()
        .optional()
        .default('')
        .describe(
            '排序方式，默认为空，即不排序。仅支持单一标识。可选标志：[startTime(出发时间从早到晚), arriveTime(抵达时间从早到晚), duration(历时从短到长)]'
        ),
    sortReverse: z
        .boolean()
        .optional()
        .default(false)
        .describe(
            '是否逆向排序结果，默认为false。仅在设置了sortFlag时生效。'
        ),
    limitedNum: z
        .number()
        .min(0)
        .optional()
        .default(0)
        .describe('返回的余票数量限制，默认为0，即不限制。'),
    format: z
        .string()
        .regex(/^(text|csv|json)$/i)
        .default('text')
        .optional()
        .describe(
            '返回结果格式，默认为text，建议使用text与csv。可选标志：[text, csv, json]'
        ),
},
  • src/index.ts:350-361 (helper)
    parseTicketsData: parses raw pipe-delimited strings from 12306 into TicketData objects using TicketDataKeys.
    function parseTicketsData(rawData: string[]): TicketData[] {
    const result: TicketData[] = [];
    for (const item of rawData) {
        const values = item.split('|');
        const entry: Partial<TicketData> = {};
        TicketDataKeys.forEach((key, index) => {
            entry[key] = values[index];
        });
        result.push(entry as TicketData);
    }
    return result;
}
  • src/index.ts:363-407 (helper)
    parseTicketsInfo: converts TicketData into TicketInfo objects with parsed prices, dates, and station names from the map.
    function parseTicketsInfo(
    ticketsData: TicketData[],
    map: Record<string, string>
): TicketInfo[] {
    const result: TicketInfo[] = [];
    for (const ticket of ticketsData) {
        const prices = extractPrices(
            ticket.yp_info_new,
            ticket.seat_discount_info,
            ticket
        );
        const dw_flag = extractDWFlags(ticket.dw_flag);
        const startHours = parseInt(ticket.start_time.split(':')[0]);
        const startMinutes = parseInt(ticket.start_time.split(':')[1]);
        const durationHours = parseInt(ticket.lishi.split(':')[0]);
        const durationMinutes = parseInt(ticket.lishi.split(':')[1]);
        const startDate = parse(
            ticket.start_train_date,
            'yyyyMMdd',
            new Date()
        );
        startDate.setHours(startHours, startMinutes);
        const arriveDate = startDate;
        arriveDate.setHours(
            startHours + durationHours,
            startMinutes + durationMinutes
        );
        result.push({
            train_no: ticket.train_no,
            start_date: format(startDate, 'yyyy-MM-dd'),
            arrive_date: format(arriveDate, 'yyyy-MM-dd'),
            start_train_code: ticket.station_train_code,
            start_time: ticket.start_time,
            arrive_time: ticket.arrive_time,
            lishi: ticket.lishi,
            from_station: map[ticket.from_station_telecode],
            to_station: map[ticket.to_station_telecode],
            from_station_telecode: ticket.from_station_telecode,
            to_station_telecode: ticket.to_station_telecode,
            prices: prices,
            dw_flag: dw_flag,
        });
    }
    return result;
}

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'query remaining tickets' without disclosing any behavioral traits like read-only nature, rate limits, or side effects. Minimal transparency.

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 a single, front-loaded sentence that efficiently states the tool's purpose with no wasted words. It is appropriately sized for the information conveyed.

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?

Given the tool complexity (10 parameters, no output schema), the description is minimal. It covers the basic purpose but lacks details on return values, pagination, or limitations. However, the thorough schema descriptions partially compensate.

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%, so the baseline is 3. The description adds no parameter meaning beyond what the schema provides. The schema descriptions are detailed, but the tool description itself does not compensate.

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?

The description clearly states the tool queries remaining ticket info from 12306, with a specific verb and resource. However, it does not differentiate from sibling tools like get-interline-tickets, lacking explicit distinction.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context. The schema parameters offer some implicit guidance, but the description itself is silent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Joooook/12306-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server