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 | List configured journey providers and their status without contacting provider systems. |
| search_locationsA | Find provider location IDs and exact names. Call this before search_journeys, then reuse an ID or exact name from the result. |
| search_journeysA | Search one-way journeys. Use origin and destination IDs or exact names returned by search_locations. Results include official links for continuing manually on provider sites. |
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 3 tools
Each tool covers a distinct step: listing providers (configuration), resolving locations to IDs, and searching journeys. The descriptions explicitly state the ordering dependency (call search_locations before search_journeys), leaving no room for misselection.
All three tools follow a strict verb_noun pattern (list_providers, search_locations, search_journeys) in consistent snake_case. The 'search_' prefix is used coherently for the two query tools and 'list_' for enumeration.
Three tools is minimal but each occupies a necessary stage of the search pipeline, with no filler. It sits at the thin edge of the range, but the narrow single-purpose domain justifies it.
The surface covers provider discovery, location resolution, and one-way journey search, forming a coherent lifecycle, but only one-way trips are supported — no round-trip or return-date search, and no way to fetch details for a specific journey beyond the search result.