Skip to main content
Glama
Joooook

12306-mcp

by Joooook
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript

get-tickets

Search for available train tickets on 12306 by specifying date, departure and arrival stations. Filter by train type, time range, and sort results.

Instructions

查询12306余票信息。

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / 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与csv。可选标志：[text, csv, json]",
+  "pattern": "^(text|csv|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.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. The verb '查询' indicates a read-only lookup with no side effects, which is useful baseline information. However, the description does not mention output shape, default result behavior, or quirks beyond what the schema already states.

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 a single, front-loaded sentence with no filler and no repetition of schema details. It is minimal enough to be scannable, though slightly under-specified for the complexity of the tool.

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?

For a 10-parameter tool with no annotations and no output schema, one sentence is thin. The schema covers invocation details well, including required fields and value formats, but the description leaves gaps around return-value structure and when to choose this tool over get-interline-tickets.

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 even though the description itself adds no parameter-level meaning. The schema descriptions are rich and include relative-date handling, station-code lookup hints, and train-filter flags, so the top-level description does not need to 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 states a concrete verb and resource: '查询12306余票信息' (query 12306 remaining-ticket information), so the agent can identify this as a ticket-availability lookup. It does not explicitly differentiate itself from the sibling get-interline-tickets, which also searches tickets, 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 guidance about when to use this tool versus get-interline-tickets or the station-lookup tools, nor any exclusions or prerequisites. The intended use is implied by the phrase '余票信息', but the agent is given no explicit selection criteria among the ticket-related siblings.

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