Skip to main content
Glama

get-tickets

Query available train tickets on China's 12306 railway system by providing departure date, station codes, and optional train type filters.

Instructions

查询12306余票信息。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes查询日期,格式为 "yyyy-MM-dd"。如果用户提供的是相对日期(如“明天”),请务必先调用 `get-current-date` 接口获取当前日期,并计算出目标日期。
fromStationYes出发地的 `station_code` 。必须是通过 `get-station-code-by-name` 或 `get-station-code-of-city` 接口查询得到的编码,严禁直接使用中文地名。
toStationYes到达地的 `station_code` 。必须是通过 `get-station-code-by-name` 或 `get-station-code-of-city` 接口查询得到的编码,严禁直接使用中文地名。
trainFilterFlagsNo车次筛选条件,默认为空,即不筛选。例如用户说“高铁票”,则应使用 "G"。可选标志:[G(高铁/城际),D(动车),Z(直达特快),T(特快),K(快速),O(其他),F(复兴号),S(智能动车组)]

Implementation Reference

  • The asynchronous handler function for the 'get-tickets' tool. It validates inputs, fetches ticket data from 12306 API using cookies, parses raw data into structured TicketInfo, applies train filters, and returns formatted text output.
    async ({ date, fromStation, toStation, trainFilterFlags }) => {
      // 检查日期是否早于当前日期
      if (!checkDate(date)) {
        return {
          content: [
            {
              type: 'text',
              text: 'Error: The date cannot be earlier than today.',
            },
          ],
        };
      }
      if (
        !Object.keys(STATIONS).includes(fromStation) ||
        !Object.keys(STATIONS).includes(toStation)
      ) {
        return {
          content: [{ type: 'text', text: 'Error: Station not found. ' }],
        };
      }
      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(API_BASE);
      if (cookies == null) {
        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
      );
      return {
        content: [{ type: 'text', text: formatTicketsInfo(filteredTicketsInfo) }],
      };
    }
  • Zod schema defining the input parameters for the 'get-tickets' tool: date (yyyy-MM-dd), fromStation and toStation codes, and optional trainFilterFlags.
    {
      date: z
        .string()
        .length(10)
        .describe(
          '查询日期,格式为 "yyyy-MM-dd"。如果用户提供的是相对日期(如“明天”),请务必先调用 `get-current-date` 接口获取当前日期,并计算出目标日期。'
        ),
      fromStation: z
        .string()
        .describe(
          '出发地的 `station_code` 。必须是通过 `get-station-code-by-name` 或 `get-station-code-of-city` 接口查询得到的编码,严禁直接使用中文地名。'
        ),
      toStation: z
        .string()
        .describe(
          '到达地的 `station_code` 。必须是通过 `get-station-code-by-name` 或 `get-station-code-of-city` 接口查询得到的编码,严禁直接使用中文地名。'
        ),
      trainFilterFlags: z
        .string()
        .regex(/^[GDZTKOFS]*$/)
        .max(8)
        .optional()
        .default('')
        .describe(
          '车次筛选条件,默认为空,即不筛选。例如用户说“高铁票”,则应使用 "G"。可选标志:[G(高铁/城际),D(动车),Z(直达特快),T(特快),K(快速),O(其他),F(复兴号),S(智能动车组)]'
        ),
    },
  • src/index.ts:684-780 (registration)
    Registration of the 'get-tickets' tool using McpServer.tool(), including name, description, input schema, and handler function.
    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-name` 或 `get-station-code-of-city` 接口查询得到的编码,严禁直接使用中文地名。'
          ),
        toStation: z
          .string()
          .describe(
            '到达地的 `station_code` 。必须是通过 `get-station-code-by-name` 或 `get-station-code-of-city` 接口查询得到的编码,严禁直接使用中文地名。'
          ),
        trainFilterFlags: z
          .string()
          .regex(/^[GDZTKOFS]*$/)
          .max(8)
          .optional()
          .default('')
          .describe(
            '车次筛选条件,默认为空,即不筛选。例如用户说“高铁票”,则应使用 "G"。可选标志:[G(高铁/城际),D(动车),Z(直达特快),T(特快),K(快速),O(其他),F(复兴号),S(智能动车组)]'
          ),
      },
      async ({ date, fromStation, toStation, trainFilterFlags }) => {
        // 检查日期是否早于当前日期
        if (!checkDate(date)) {
          return {
            content: [
              {
                type: 'text',
                text: 'Error: The date cannot be earlier than today.',
              },
            ],
          };
        }
        if (
          !Object.keys(STATIONS).includes(fromStation) ||
          !Object.keys(STATIONS).includes(toStation)
        ) {
          return {
            content: [{ type: 'text', text: 'Error: Station not found. ' }],
          };
        }
        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(API_BASE);
        if (cookies == null) {
          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
        );
        return {
          content: [{ type: 'text', text: formatTicketsInfo(filteredTicketsInfo) }],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. '查询' (query) implies a read-only operation, but the description doesn't explicitly state whether this requires authentication, has rate limits, returns paginated results, or what happens on errors. For a ticket query tool with zero annotation coverage, this represents significant behavioral gaps that could affect agent decision-making.

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 extremely concise at just 8 Chinese characters ('查询12306余票信息'), making it front-loaded and efficient with zero wasted words. Every character serves the purpose of identifying the tool's function. This represents optimal conciseness for a tool description.

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

Completeness2/5

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

Given the complexity of a ticket query system with 4 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what information is returned (ticket types, prices, availability status), how results are structured, or any behavioral constraints. The agent would need to infer too much about this tool's operation from the minimal description.

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?

The description provides no parameter information beyond what's already in the schema. With 100% schema description coverage, all 4 parameters (date, fromStation, toStation, trainFilterFlags) are well-documented in the schema with format requirements, dependencies on other tools, and usage examples. The baseline score of 3 reflects that the schema does the heavy lifting while the description adds no additional parameter semantics.

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 '查询12306余票信息' clearly states the purpose as querying ticket availability from the 12306 system. It specifies the verb '查询' (query) and resource '余票信息' (ticket availability), making the tool's function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get-interline-tickets' which might handle different ticket types or routes.

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

Usage Guidelines3/5

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

The description provides implied usage context through the Chinese text, suggesting it's for checking ticket availability on China's 12306 railway system. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get-interline-tickets' or when not to use it. The input schema provides some usage hints (like calling other tools first for date/station codes), but these aren't part of the description itself.

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/freestylefly/12306-mcp'

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