sixflags-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIXFLAGS_HOME_PARK | No | Default park for tools that don't name one. A park name, themeparks.wiki slug, or park id. | Carowinds |
| SIXFLAGS_USER_AGENT | No | User-Agent sent to themeparks.wiki. | sixflags-mcp (+…) |
| SIXFLAGS_REQUEST_TIMEOUT_MS | No | Per-request timeout. | 15000 |
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 |
|---|---|
| sixflags_list_parksA | List Six Flags parks (the combined Six Flags / Cedar Fair chain, including Carowinds, Cedar Point, Canada’s Wonderland, Magic Mountain, and the Hurricane Harbor water parks). Optionally filter by a name substring. Returns each park’s id, name, and owning destination, and flags your configured home park. |
| sixflags_get_park_scheduleA | Get operating hours (open/close times) for a Six Flags park, from today forward. Defaults to your home park. Use this to plan what time to arrive and how long you have. |
| sixflags_get_wait_timesA | Get current ride wait times for a Six Flags park (defaults to your home park, Carowinds). Returns every attraction with its status (operating/closed/down) and standby + single-rider waits, sorted longest-wait first, plus a summary of the park’s crowd level. |
| sixflags_suggest_nextA | Recommend which attraction to ride next: ranks currently-operating rides by shortest standby wait. Optionally exclude rides you’ve already done and cap the wait. Use this repeatedly through the day to keep hopping to the lowest-wait ride. Defaults to your home park (Carowinds). |
| sixflags_list_attractionsA | List the attractions (or shows / restaurants) at a Six Flags park — the full directory of what’s there, with map coordinates. Static metadata, not live status; use sixflags_get_wait_times for current waits. Defaults to your home park (Carowinds). |
| sixflags_get_showsA | Get today’s live show schedule (showtimes) for a Six Flags park — parades, stunt shows, character meets. Defaults to your home park (Carowinds). Showtimes are only populated on operating days. |
| sixflags_healthcheckA | Check that the upstream data source (themeparks.wiki) is reachable and returning Six Flags park data. Returns ok/degraded plus the number of parks discovered. |
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 7 tools
Each tool targets a distinct data type (parks, hours, waits, attractions, shows) with clear separation between static and live data. The only overlap is sixflags_suggest_next, which is derived from sixflags_get_wait_times, but its recommendation framing sets it apart.
All tools share the sixflags_ prefix and follow a verb_noun pattern (list_parks, get_wait_times, list_attractions). Minor deviations: sixflags_healthcheck is noun-only and sixflags_suggest_next is verb+adverb rather than verb_noun.
Seven tools is well-scoped for a park-planning server, with each tool covering a distinct capability (discovery, planning, live status, recommendations, diagnostics). No redundant or filler tools.
Covers the core planning lifecycle: find parks, check hours, view waits, get recommendations, browse attractions/shows, plus a healthcheck. Minor gaps exist around park closures/alerts and dining detail, but the main agent workflows are supported.