io.github.mohammad-abbasi-sh/flixtrain-mcp

flixtrain_search_trains

Search FlixTrain-only departures between two cities on a specific date, returning departure times, stations, duration, prices, and seat availability. Limit results and sort by departure or price.

Instructions

Search FlixTrain-only departures between two cities on a date. from_city / to_city: city names, e.g. Berlin, Hamburg, Köln (Cologne). date: DD.MM.YYYY, e.g. 11.11.2026. limit: 1..20 (default 10). sort: departure (default) or price.

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": {
      "from_city": "<from_city>",
      "to_city": "<to_city>",
      "date": "<date>"
    },
    "name": "flixtrain_search_trains"
  }
}

Input Schema

Name	Required	Default
`date`	Yes
`sort`	No	departure
`limit`	No
`to_city`	Yes
`from_city`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.7/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 full behavioral burden. It does disclose meaningful scope ('FlixTrain-only' — no other operators) and format/range constraints, but says nothing about whether prices are live, how results behave when no departures match, or any auth/rate characteristics. Since an output schema exists, return-shape explanation is not required.

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?

Front-loaded purpose sentence followed by tight per-parameter lines, one clause each, no filler. Everything present is either scope or format information an agent needs.

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 five-parameter, three-required tool with no annotations and an output schema, the description covers purpose, scope, all parameter formats and defaults. Minor omissions are edge-case behavior (zero results, ambiguous city names) rather than anything blocking a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: it defines from_city/to_city with concrete examples, the date format DD.MM.YYYY with an example, limit range 1..20 with default, and sort values with default. Remaining gaps are city-name matching behavior (accents, Cologne vs Köln) and what other sort values exist.

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?

States a specific verb and resource: 'Search FlixTrain-only departures between two cities on a date.' The 'FlixTrain-only' qualifier gives real scope, but it does not name or route against the sibling flixtrain_search_cities, leaving that differentiation to the agent.

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?

Usage is only implied — an agent can infer this is the tool for finding train departures once city names are known. There is no explicit when-to-use/when-not, and no pointer to flixtrain_search_cities for resolving ambiguous city names, which would have been the obvious pairing.

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

Deploy Server