Skip to main content
Glama
Joooook

12306-mcp

by Joooook
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript

get-interline-tickets

Search for interline (transfer) train tickets on 12306. Filter by date, stations, departure time, train type, and more to find available transfer options.

Instructions

查询12306中转余票信息。尚且只支持查询前十条。

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • changedInput schema / properties / fromStation / description
      Previous value: -"出发地的 `station_code` 。必须是通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到的编码，严禁直接使用中文地名。"New value: +"出发地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）"
    • changedInput schema / properties / middleStation / description
      Previous value: -"中转地的 `station_code` ，可选。必须是通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到的编码，严禁直接使用中文地名。"New value: +"中转地的中文或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）。该参数可选。"
    • changedInput schema / properties / toStation / description
      Previous value: -"出发地的 `station_code` 。必须是通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到的编码，严禁直接使用中文地名。"New value: +"到达地的中文名或站点的 `station_code`（可通过 `get-station-code-by-names` 或 `get-station-code-of-citys` 接口查询得到）"
  2. Changed3 schema fields changedv1.0.0
    • addedInput schema / properties / earliestStartTime
      Added value: +{
+  "default": 0,
+  "description": "最早出发时间（0-24），默认为0。",
+  "maximum": 24,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / format
      Added value: +{
+  "default": "text",
+  "description": "返回结果格式，默认为text，建议使用text。可选标志：[text, json]",
+  "pattern": "^(text|json)$",
+  "type": "string"
+}
    • addedInput schema / properties / latestStartTime
      Added value: +{
+  "default": 24,
+  "description": "最迟出发时间（0-24），默认为24。",
+  "maximum": 24,
+  "minimum": 0,
+  "type": "number"
+}
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does reveal a key limitation ('尚且只支持查询前十条'), which is not apparent from the schema's unlimited limitedNum parameter. However, it does not describe the return structure, error behavior, or other side-effect profile, so coverage is partial.

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?

The description is only two short sentences with no filler, and the key limitation is included. It could be slightly more informative in the first sentence, but overall it is appropriately concise for a tool whose parameters are well-documented in the schema.

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?

This is a 12-parameter tool with no output schema and no annotations, yet the description only states the resource and a ten-result limitation. It omits the return format, how to interpret results, and any relationship to direct-ticket queries. The rich schema mitigates parameter confusion but does not make the overall description complete.

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 schema already documents all 12 parameters with meanings and defaults. The description adds no parameter-level detail beyond hinting at an effective ten-result cap, which actually creates slight ambiguity with the unlimited limitedNum field. Baseline 3 is appropriate.

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 operation ('查询') and resource ('12306中转余票信息'), and the word '中转' distinguishes it from the sibling tool get-tickets, which likely handles direct tickets. However, it does not explicitly name the alternative or state 'use this for transfer searches only,' so it stops short of full sibling differentiation.

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?

There is no explicit guidance about when to use this tool versus get-tickets or the station-lookup siblings. The transfer-ticket scope is only implicit in the description and tool name, and no exclusions or alternative conditions are mentioned.

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