Alice Flights
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 |
|---|---|
| search_flightsA | Search for available flights between two cities. 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 |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined as flight search, making its role unambiguous.
The single tool name 'search_flights' follows a clear verb_noun pattern, and since there is only one tool, there is no inconsistency to evaluate.
The server exposes only one tool, which feels thin for a flight-related service. While it may be sufficient for a search-only endpoint, it falls below the typical 3-15 tool range and leaves the impression of an underprovisioned server.
The tool covers basic flight search but lacks essential parameters like travel dates or passenger count, and there are no booking or management tools. This results in significant gaps for a flight service domain.