italian-bus-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_providersA | BUS ONLY. List configured bus/coach providers and their status. Never use this tool for trains or rail; use list_train_providers instead. |
| list_train_providersA | TRAINS ONLY. Use for requests involving trains or rail. Lists train operators and whether schedule, price, live-status, and station-board capabilities are enabled. |
| search_locationsA | BUS ONLY. Find bus/coach location IDs and exact names. Never use for train stations; use search_train_locations instead. For an aggregate bus search, reuse exact names shared across providers. |
| search_journeysA | BUS ONLY. Search one-way bus/coach journeys. Never use for trains or rail; use search_train_journeys instead. Results include official links for continuing manually on provider sites. For stable pagination start with snapshot:true; continue using only searchId, offset and limit. |
| search_train_locationsA | TRAINS ONLY. Use for every request involving trains or rail to find operator-aware stations. Prefer names across operators; station IDs are operator-specific. |
| search_train_journeysA | TRAINS ONLY. Requires origin, destination, and date. When the user states passenger counts, always pass adults and children explicitly. Each price is the total for those passengers; never infer discounts or convert it to a per-person price. For stable pagination start with snapshot:true; continue using only searchId, offset and limit. |
| get_train_statusB | Get live status using operator, train number, service date, and origin identity. Live status may be unavailable independently of schedules. |
| get_station_boardB | Get an operator station board with its observation timestamp. Live boards may be unavailable independently of schedules. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct scope, reinforced by explicit BUS ONLY / TRAINS ONLY markers and warnings against cross-use. Paired tools like search_locations vs search_train_locations and list_providers vs list_train_providers are easy to tell apart.
All names follow a snake_case verb_noun pattern, so the set is highly readable. Minor inconsistency appears in qualifiers: some train-specific tools include train, but get_station_board does not, and list_providers is generic while list_train_providers is explicit.
Eight tools is well-scoped for a bus search server that also exposes train search/status capabilities. Each tool has a clear role and no obvious redundancy.
The surface covers providers, locations, journey search, station boards, and live train status, which is strong for a search aggregator. Minor gaps exist around inspecting a specific journey or deeper station/stop details, but core workflows are covered.