China 12306 Train Tickets MCP

Search Station

search_station

按关键词搜索12306车站名称，返回匹配的车站中文名列表。不确定城市有哪些车站时使用。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "search_station"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	关键词，如 "北京"

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 9, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / keyword / description
```
Added value: +"关键词，如 \"北京\""
```
- removedInput schema / properties / keyword / title
```
Removed value: -"Keyword"
```
- removedInput schema / title
```
Removed value: -"search_stationArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
```
First observedSep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the read-style behavior and the shape of the result (matching Chinese station names), but says nothing about fuzzy vs exact matching, empty-result behavior, or authentication needs; an output schema covers the return format.

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?

Two short sentences, front-loaded with purpose and result, second sentence reserved for usage. No filler, though the matching semantics could be tightened without adding length.

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

Completeness4/5

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

For a single-parameter lookup with a full schema description and an output schema, this is close to sufficient; only matching behavior and result limits remain unspecified, which are minor for such a simple tool.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself giving the example '北京'. The description restates that the keyword targets station names, adding slight meaning over the schema but no format or matching rules.

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 names a specific verb (搜索/search) and resource (12306车站名称), plus the returned artifact (匹配的车站中文名列表). It does not explicitly differentiate itself from query_train_tickets, but the station-name lookup scope is unambiguous on its own.

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

Usage Guidelines4/5

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

'不确定城市有哪些车站时使用' gives an explicit triggering condition for the tool. It stops short of stating when NOT to use it or naming query_train_tickets as the alternative when the user already knows the station.

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

All China 12306 Train Tickets MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.