Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REGIOJET_LANGNoLanguage used for API responses.en
REGIOJET_USERNoUsername for HTTP Basic auth for affiliate accounts. Ignored when REGIOJET_API_KEY is set.
REGIOJET_API_KEYNoRegioJet customer account token (sent as Bearer). Enables the account tools (booking, payment, cancellation).
REGIOJET_TIMEOUTNoHTTP request timeout in seconds.20
REGIOJET_BASE_URLNoBase URL of the RegioJet Affiliate API.https://brn-ybus-pubapi.sa.cz/restapi
REGIOJET_CURRENCYNoCurrency used for prices.EUR
REGIOJET_MCP_HOSTNoHost to bind when using the http transport.127.0.0.1
REGIOJET_MCP_PORTNoPort to bind when using the http transport.8000
REGIOJET_PASSWORDNoPassword for HTTP Basic auth for affiliate accounts. Ignored when REGIOJET_API_KEY is set.
REGIOJET_MCP_TRANSPORTNoMCP transport to use, e.g. stdio or http.stdio

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_locationsA

Find RegioJet cities and stations by name. Use returned id+type as from/to in search_routes.

Prefer CITY ids for searching (covers all stations in the city); STATION ids are needed for route detail/seats.

search_routesB

Search RegioJet connections between two locations on a date. Returns route ids for get_route_detail.

get_route_detailB

Get a route's sections (trains/buses, lines, platforms, transfers) and price per seat class.

get_free_seatsA

Get free seats per vehicle (carriage/bus) offering the given seat class, for each section of a route.

Double-decker buses are one vehicle with several decks; seats are listed per deck.

list_tariffsB

List passenger tariffs (adult, child, student, senior, ...). Use key in tariffs arguments.

list_seat_classesB

List seat classes (Low cost, Standard, Relax, Business, ...) with descriptions.

list_vehicle_standardsB

List vehicle standards (e.g. YELLOW, FUN_AND_RELAX) with descriptions.

list_carriersB

List carriers operating RegioJet connections.

list_action_pricesC

List marketing actions / promo prices.

get_ticketA

Get an existing ticket by account code and ticket id.

get_accountA

Get the logged-in RegioJet account: name, default tariff and credit balance.

list_my_ticketsA

List tickets and reservations on the logged-in account, newest first.

get_my_ticketA

Get one ticket of the logged-in account: state, seats, price, unpaid amount, cancel conditions.

create_reservationA

Reserve seats on the logged-in account. The reservation is UNPAID and expires at expiration_date unless paid (pay_ticket_with_credit, or in the RegioJet app/web) or cancelled first.

pay_ticket_with_creditA

Pay UNPAID tickets from the account's RegioJet credit. Spends real money: confirm with the user first.

cancel_ticketA

Cancel a reservation or a paid ticket. Paid tickets may incur cancel_charge (see get_my_ticket). Confirm with the user first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
tariffs_resourcePassenger tariffs.
seat_classes_resourceSeat classes.

TDQS

A3.5/5.0

Scored across 16 tools

Disambiguation4/5

Most tools have clear, distinct roles: location lookup, route search/detail, seat availability, reference lists, and the account/ticket lifecycle are well separated. The one weak spot is the trio get_ticket / get_my_ticket / list_my_tickets, where the boundary between retrieving 'an existing ticket by account code' and 'one ticket of the logged-in account' requires careful reading of descriptions.

Naming Consistency5/5

All names are snake_case verb_noun (get_ticket, search_routes, list_seat_classes, create_reservation, cancel_ticket), with consistent get_/list_/find_/search_/create_/cancel_/pay_ prefixes. Exceptions like pay_ticket_with_credit still fit the verb-first convention and remain readable.

Tool Count4/5

16 tools is at the upper bound but justified by the domain: five cheap list_* reference lookups (tariffs, seat classes, vehicle standards, carriers, action prices) support the core search/book/pay flow. A couple of the list endpoints (carriers, vehicle standards) are marginally useful, so it is slightly over-scoped rather than well-scoped.

Completeness4/5

The booking lifecycle is well covered end-to-end: locate stations, search routes, inspect detail/seats, reserve, pay with credit, and cancel, plus account and ticket retrieval. The main gap is the absence of a modify/update-reservation operation, forcing users to cancel and recreate; there is also no explicit passenger-detail handling visible in the surface.

Maintenance

ActivityMaintained
ResponsivenessSyncing