Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LUMA_API_KEYYesAPI key generated from https://lu.ma/settings/api
MYCELIUM_NO_PINGNoOpt out of telemetry ping by setting to '1'

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
luma_healthA

Verify the LUMA_API_KEY is set and authenticates against the Luma API.

Returns the calling user's profile on success (proves the key works) plus the active draft count so the operator can see if anything is staged.

luma_cancel_draftC

Cancel an unconfirmed draft. Idempotent.

luma_create_event_draftA

Stage an event for creation. Nothing posts to Luma until confirm.

luma_create_event_confirmA

Commit a previously-drafted event creation. Returns the new event.

luma_update_event_draftC

Stage an event update. Only fields provided are changed.

luma_update_event_confirmB

Commit a previously-drafted event update.

luma_get_eventA

Fetch one event by ID. Returns the typed shape plus the raw payload.

luma_list_eventsA

List events on the API key's calendar. Pagination via after/before cursors.

luma_create_ticket_type_draftA

Stage a ticket type for an event. Nothing posts until confirm.

Pass either price_usd (decimal, e.g. 250.0) or cents (integer, e.g. 25000). Setting both raises. Setting neither creates a free ticket.

luma_create_ticket_type_confirmA

Commit a previously-drafted ticket type.

luma_create_coupon_draftA

Stage a coupon. Nothing posts until confirm.

Pass exactly one of discount_percentage or discount_cents.

luma_create_coupon_confirmB

Commit a previously-drafted coupon.

luma_list_couponsA

List coupons scoped to an event (or calendar-wide if event_id is None).

luma_list_event_guestsB

List RSVPs / guests for an event.

luma_send_event_email_draftB

Stage an email blast to event attendees. Body markdown supported.

luma_send_event_email_confirmC

Commit a previously-drafted attendee email blast.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 16 tools

Disambiguation5/5

Each tool has a distinct purpose: health check, event CRUD with draft/confirm pattern, ticket types, coupons, guests, and email blasts. No overlapping functionality, and descriptions clearly differentiate operations.

Naming Consistency5/5

All tools follow a consistent 'luma_verb_noun' pattern with underscores. Verbs are intuitive (create, update, list, get, cancel, send) and nouns describe the resource (event, ticket_type, coupon, guest). Very predictable.

Tool Count5/5

16 tools is a well-scoped set for an event management API. It covers draft/confirm workflows, listing, and auxiliary operations without unnecessary bloat or missing essentials.

Completeness4/5

Core event lifecycle (create, update, get, list, cancel drafts) is covered, plus ticket types, coupons, guests, and email sending. Missing: ability to delete confirmed events or update ticket types/coupons after creation. Minor gaps but overall comprehensive.

Maintenance

ActivityActive
ResponsivenessUnresponsive