good_wook
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PHISHNET_API_KEY | Yes | Your Phish.net API key (v5 required). Request at https://phish.net/api. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Health check and a manifest of what good_wook can do. |
| get_setlistC | Phish setlist for a given date (YYYY-MM-DD). |
| latest_showC | The most recent show's setlist. |
| this_day_in_historyA | Every show played on a given calendar day (month 1-12, day 1-31), across years. |
| search_showsB | Find shows by year, city, and/or venue name. |
| random_showA | A random Phish show, with its full setlist. |
| song_historyD | Every time a song has been played (most recent first). |
| song_statsC | Stats for a song: times played, debut, last played, current gap, jamchart count. |
| jam_chartA | Notable jams from the Phish.net jam charts, optionally filtered to one song. |
| venue_infoC | Venue metadata plus how many times Phish has played there. |
| upcoming_showsB | Announced upcoming shows (dates on or after today). |
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 11 tools
Each tool targets a distinct query type: specific date setlists, random/latest showcases, historical calendar lookup, search, song history/stats, jam charts, venue info, and upcoming shows. Even the setlist-returning tools are clearly differentiated by their selection criteria.
Tool names are all lowercase snake_case and mostly descriptive, but they mix verb-prefixed names (get_setlist, search_shows) with bare noun phrases (random_show, latest_show, song_history). This inconsistency is noticeable but the meaning is still clear.
11 tools is well within the ideal 3-15 range. Each tool serves a specific fan-facing query need, and there is no bloat or redundancy in the count.
The surface covers the core Phish setlist database use cases: specific dates, random/latest, historical day, search, song-level history/stats, jam charts, venue info, and upcoming shows. Minor gaps exist like tour-based filtering or setlist-by-ID, but agents can generally accomplish what they need.