Go2Trip
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GO2TRIP_MCP_URL | No | The hosted server to forward to. Leave unset. | https://mcp.go2trip.com/mcp |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_flightsA | Search flights between any two cities worldwide on Go2Trip. Returns a curated set of options, each tagged with one or more categories:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ui://go2trip/flights.html | Interactive flight results — compare best, cheapest and fastest options side by side and open one to book. |
TDQS
Scored across 1 tool
With a single tool there is no possibility of misselection, and its purpose (searching flights between two cities) is stated unambiguously. The category semantics (best/cheapest/fastest) are explained inline, so an agent knows exactly what the one tool returns.
The single tool name `search_flights` follows a clean verb_noun snake_case convention that matches its action. There is no competing convention to create inconsistency.
One tool is thin even for a narrowly scoped flight-search server; common adjacent needs (get flight details, filter by date range, multi-city, or fare rules) have no entry point. It is defensible as a minimal search surface but leaves the agent with only a single lever.
Search is well covered and returns rich metadata plus a booking link, which mitigates the missing booking operation. However there are notable gaps: no way to retrieve details for a specific itinerary, refine by cabin/airline/date window, or handle round-trip/multi-city searches.