better_luma
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSH_JWT_TOKEN | No | Optional Posh JWT | |
| PARTIFUL_AUTH_TOKEN | No | Optional Partiful bearer token | |
| LUMA_AUTH_SESSION_KEY | No | Optional Luma session key for private reads | |
| BETTER_LUMA_AUTH_TOKEN | No | Backwards-compatible alias for LUMA_AUTH_SESSION_KEY | |
| BETTER_LUMA_API_BASE_URL | No | WAP FastAPI base URL | http://127.0.0.1:8000 |
| BETTER_LUMA_SCRAPE_TIMEOUT_SECONDS | No | Long scrape request timeout | 180 |
| BETTER_LUMA_REQUEST_TIMEOUT_SECONDS | No | Normal backend request timeout | 30 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | Check whether the Better Luma/WAP backend is available. |
| list_citiesA | List cities supported by an event platform. |
| list_event_typesA | List the backend's event category filters for one platform. |
| list_eventsB | List events from Luma, Posh, or Partiful. |
| get_eventB | Get details for one event ID or Luma URL slug. |
| search_eventsA | Search event names and descriptions on one platform. |
| get_event_guestsB | Get an event guest list when the platform permits access. |
| scrape_cityB | Collect events and visible attendees without automatically RSVPing. |
| list_my_luma_eventsA | List the authenticated user's managed, upcoming, or past Luma events. |
| verify_luma_hostA | Check whether the authenticated Luma user hosts an event. |
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 10 tools
Most tools target distinct actions, but some overlap exists: list_events and scrape_city both collect events, get_event_guests and scrape_city both collect attendees, and list_my_luma_events overlaps with verify_luma_host in checking host status. The descriptions reduce ambiguity but the boundaries are not always crisp.
The naming pattern is mostly consistent verb_noun snake_case, e.g. list_events, get_event, search_events, verify_luma_host. The lone 'health' tool breaks the pattern by not using a verb, though it is still understandable.
Ten tools is a well-scoped count for an event aggregation/read-only API. Each tool covers a distinct aspect of the domain without unnecessary bloat or obvious redundancy.
The toolset covers the core read-only workflow: event types, cities, event listing/search/detail, guests, city scraping, and authenticated user event queries. Minor gaps exist such as no explicit platform-list tool or direct attendee export beyond guests, but agents can mostly accomplish the intended tasks.