waypoint-airports
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRPORT_API_URL | Yes | FastAPI address used by the Streamlit dashboard and MCP client. |
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 |
|---|---|
| suggest_travel_airportsB | Suggest nearby departure and destination airports using the local Open Airports dataset. |
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 a single tool, there is no possibility of confusing it with another tool in the set. Its purpose is unambiguous.
suggest_travel_airports follows a clear verb_noun snake_case convention, but with only one tool there is no pattern to demonstrate consistency against.
A single tool is thin for a server, though it matches a narrow, single-purpose scope of suggesting airports. It borders on under-scoped.
The tool covers the core suggestion action, but there is no way to look up airport details, list airports, or retrieve metadata, leaving notable gaps for a broader airport domain.