Skip to main content
Glama

SiteCheck Shop & Social

FlixBus and FlixTrain trips between two cities on a date

ecommerce_flixbus
Read-only

FlixBus and FlixTrain trips between two cities on a date: departure and arrival times and stations, duration, number of transfers, price in EUR (with and without platform fee), seats left and availability status, from FlixBus's public search API. One adult, one way. Related tools on this server, for a different need: ecommerce_aliexpress when you need AliExpress product search from the public search page; ecommerce_backmarket when you need Back Market refurbished-product search on a country site. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "<from>",
      "to": "<to>"
    },
    "name": "ecommerce_flixbus"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesArrival city name, e.g. Munich (required)
dateNoTravel date YYYY-MM-DD, today to 180 days ahead (default: 7 days from today)
fromYesDeparture city name, e.g. Berlin (required)

Output Schema

NameRequiredDescriptionDefault
toNo
dateNo
fromNo
countNo
tripsNo
sourceNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the upstream source (FlixBus public search API), the pricing model ($0.002 USDC per successful call via x402 on Base/Solana/Arc) and the fact that failed calls are not charged. That payment/authorization context is exactly what an agent needs before invoking a paid endpoint. It does not cover rate limits or empty-result behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and the return-field list is efficient, but the middle sentence cross-selling AliExpress and Back Market is off-topic filler that does not help an agent call this travel tool. The pricing sentence is long but does carry required billing information.

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?

With an output schema present, the definition need not explain return shape, and it still summarizes the key fields, the source, the cost model, and the one-way/one-adult assumption. Only minor operational details (defaults, failure modes, whether city names must match station naming) are left unstated.

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 coverage is 100%, so city names and the YYYY-MM-DD format are already fully documented. The description adds only the constraint that results are for one adult, one-way, which does clarify how 'from'/'to' are interpreted but is marginal over the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: FlixBus and FlixTrain trips between two cities on a date, then enumerates exactly what is returned (times, stations, duration, transfers, EUR price with/without fee, seats left, availability). Title and description agree, and no sibling on this server does intercity transport, so an agent can identify it immediately.

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?

Constraints such as 'one adult, one way' and the date window (in the schema) frame expected use, but there is no explicit when-to-use/when-not guidance. The 'related tools' sentence points at AliExpress and Back Market product search, which are not alternatives for a travel query, so it does not actually help route between competing tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources